It's been a very long and crazy ride but I'm happy to share that the project I've been working so hard since I joined the npm team more than an yea...
For further actions, you may consider blocking this person and/or reporting abuse
I was curious, What does the NPM team(s) think of PNPM and if there are plans to build something similar?
Personally, I think very highly of pnpm and Yarn (and their respective maintainers) as I think they brought up (and still do) a lot of innovation to JS package managers - that said, we are often going to be looking at what they are bringing to the table as a source of inspiration rather than reproducing their solution to a specific problem.
I believe when you say "if there are plans to build something similar?" you are referring to their "non-flat node_modules" structure π€ but regardless the answer is the same: npm has its own way of doing things and solving the dependency management problem and while we'll be inspired by the work of other package managers we won't necessarily change our system to simply replicate a different one.
Now if any major changes (such as implementing a
symlink-based non-flat node_modules folder
) were to be implemented, the place to keep an eye is the npm RFCs repo where we have discussions with the community on how to change the cli for the better πSorry this turned into a long answer but it was a good question that I felt like needed a more elaborate response π Thanks and all the best!
I was more referring to how pnpm uses symlinks to reduce disk and network usage (and install times!). Could be a very big benefit in developing countries where everyone isn't on a Mac.
Great answer though! I prefer the long answers, shows you're really excited
Keep up the great work!
I am curious about backward compatibility. Does an old project break if I will try to use the new npm or not? :D (probably not, but the golder rule: do not upgrade anything until you are not released and hotfixed the product)
One of the goals is to try and minimize the breaking changes π but since this is a major version bump there are a few to be expected - in all cases if you want to err on the side of safety then the best thing to do is to wait until v7 lands on npm
latest
tag as mentioned in the GitHub blog post (that is going to be our equivalent of a LTS release) πCongrats on the release @ruyadorno and team! π₯
Amazing news!!!!!! β€οΈπππ
merry npm!
Congrats!!
astonishing news =]
Congrats!
Cool!