Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • 16:01

    zkochan on main

    feat(core): overrides, packageE… (compare)

  • 16:01

    zkochan on refactor-overrides

    (compare)

  • 16:01
    zkochan closed #4050
  • 15:22
    vivek-medly commented #2933
  • 14:31
    damiensedgwick commented #2933
  • 13:41
    erlendk commented #3755
  • 13:37
    cjanietz commented #2933
  • 13:37
    cjanietz commented #2933
  • 13:30
    zkochan synchronize #4050
  • 13:30

    zkochan on refactor-overrides

    test: getOptionsFromRootManifes… (compare)

  • 13:29
    zkochan review_requested #4050
  • 12:48
    zkochan synchronize #4050
  • 12:48

    zkochan on refactor-overrides

    refactor: core (compare)

  • 12:37
    zkochan synchronize #4050
  • 12:37

    zkochan on refactor-overrides

    docs: update changesets (compare)

  • 12:35
    zkochan synchronize #4050
  • 12:35

    zkochan on refactor-overrides

    fix: unlink (compare)

  • 11:10
    zkochan synchronize #4050
  • 11:10

    zkochan on refactor-overrides

    docs: add changesets (compare)

  • 11:03
    zkochan review_requested #4050
Zoltan Kochan
@zkochan
hm, if you know how to explain it better, you can suggest an edit. We can definitely extend the FAQ section
Amit Marcus
@marxus85
aight! i'll think about it. anyway, thanks for clearing this out for me
Zoltan Kochan
@zkochan
you're welcome
Amit Marcus
@marxus85
this is actually cool, both places point to the same file, but if i delete only one of them the other one is still there.. nice
Zoltan Kochan
@zkochan
yes, but I work on a mixed solution now because creating one symlink to the folder is faster than creating many hard links to each file
pnpm/pnpm#791
when a package is "independent" it can be symlinked
Amit Marcus
@marxus85
ok that something i didnt not understand in the first place, i mean why not just junctioning all the folders to begin with..
Zoltan Kochan
@zkochan
because packages have different sets of dependencies in different projects
Zoltan Kochan
@zkochan

@all pnpm version 0.70.0 has been released. Not as latest for now.

It has breaking changes in the store structure, so you'll have to reinstall node_modules.

However, it is the fastest pnpm so far!

Vaughan Rouesnel
@vjpr
nice work!
Zoltan Kochan
@zkochan
It would be great to have some help resolving the webpack/browserify issues: pnpm/pnpm#801
Zoltan Kochan
@zkochan
Seems like pnpm has no issues with the latest webpack! This is great! Now pnpm can be used for CRA and Angular2
Andrey Popp
@andreypopp
btw lockfiles
I like that npm5 locks the structure — I think it's more readable than yarn's approach where it maps ranges to concrete versions
The improvement, I think would be to have a flat structure like yarn but with dependent: package-name field on each record which specifies the package which depends on the record's package
Zoltan Kochan
@zkochan
Zoltan Kochan
@zkochan
I'll write a post about pnpm's shrinkwrap format. But ours doesn't need to fix layout because pnpm is not hoisting packages.
our's is also good for CR because we use YAML not JSON
and we show structure, by having dependencies and optionalDependencies in each package. So no need in dependent
Zoltan Kochan
@zkochan
Andrey Popp
@andreypopp
🎉🎉👍
kylemeier
@kylemeier
sorry if this was already asked but if one library requires lodash 1.5.4 and another lodash 2.7.9, does lodash get installed twice or just once and potentially breaks one of the libraries?
Zoltan Kochan
@zkochan
By once we mean. Once a concrete version
So both 1.5.4 and 2.7.9 will be installed. But only once each
Jason Yu
@ycmjason
hello there, I have a curious question. Is there a way to see which packages are available on local, i.e. already downloaded on my computer?
Zoltan Kochan
@zkochan
there is no command for it. You can look in the ~/.pnpm-store/2/store.json file
Jason Yu
@ycmjason
wouldn't it be a neat feature?
pnpm ls
then list the packages installed locally
Zoltan Kochan
@zkochan
we did not implement pnpm ls yet:-)
Jason Yu
@ycmjason
just a suggestion or random thought
Zoltan Kochan
@zkochan
oh, look, we already had this idea pnpm/pnpm#430
pnpm store ls
Zoltan Kochan
@zkochan
pnpm is now on 1st page when Google searching "fast package manager". And on first place on duckduckgo :tada:
kaiserfedor
@kaiserfedor
Hello everyone! In pnpm doc: When using npm or Yarn for example, if you have 100 packages using lodash, you will have 100 copies of lodash on disk. But it doesn't seem to be true, at least for npm. :)
it may confuse somebody
Zoltan Kochan
@zkochan
OK. I'll rewrite it.
kaiserfedor
@kaiserfedor
Thank you for your work.
Zoltan Kochan
@zkochan
so I guess I'll just replace "packages" with "projects".
inside packages dependencies duplicate as well. but that would be harder to explain in a sentence
if you have 100 projects using lodash
kaiserfedor
@kaiserfedor
:+1:
schemelev
@schemelev
has anyone been faced with the transfer of the node_modules folder to another
Zoltan Kochan
@zkochan
what do you mean?
schemelev
@schemelev
Install packages and build the project (Teamcity) occur in the temporary folder. And if successful, the project folder is transferred to a working folder.
Zoltan Kochan
@zkochan
pnpm uses symlinks. They are relative.
so I think if the temp folder is on the same level of nesting as the destination folder then it is fine
symlinks should work in the destination folder
otherwise, you can use a store that will be inside the temp folder as well
and in that case the project will be moved together with the store
but I am not sure I tried it. Maybe symlinks are fixed during folder moves? I don't know. Let us know about your findings
schemelev
@schemelev
Thank you, I will look for a solution