News for hackers. Stuff that matters.
Re:NPM Is Joining GitHub by sandov on Monday March 16, 2020 @01:05PM (#22594594)
"Github acquires npm" would be a better title IMO.
Re:NPM Is Joining GitHub by kdaigle on Monday March 16, 2020 @01:10PM (#22594678)
Today we've announced that we've signed an agreement to acquire NPM but we technically have not acquired them yet (referred to as "closed"). NPM is still their own company for now and that's why the language is future tense.
Re:NPM Is Joining GitHub by sandov on Monday March 16, 2020 @01:15PM (#22594748)
"Github is acquiring npm" then. "NPM is joining Github" sounds like you're just using Github to host your stuff.
Re:NPM Is Joining GitHub by Conan_Kudo on Monday March 16, 2020 @01:57PM (#22595342)
Using the "is joining" phrasing is a classic way to try to spin an acquisition as some kind of partnership. 99% of the time, it's definitely not.
Re:NPM Is Joining GitHub by rdiddly on Monday March 16, 2020 @04:56PM (#22597658)
I literally thought that, clicked hide, then thought "Wait a minute, do they mean...?" and had to go fish it out of hidden items.

"Joining" is an interesting term here... but I suppose it won because it sounds more like something friendly humans would do. "NPM Is Breaking Bread and Sharing with Github as Special Friends."

Re:NPM Is Joining GitHub by TheKarateKid on Monday March 16, 2020 @02:28PM (#22595732)
Then saying "GitHub is acquiring NPM" would've been a more accurate way to say this.
Re:NPM Is Joining GitHub by hinkley on Monday March 16, 2020 @01:11PM (#22594687)
I am glad that the npm team will finally have some adult supervision.

Meanwhile, I almost have my team switched to yarn.

Re:NPM Is Joining GitHub by SahAssar on Monday March 16, 2020 @01:38PM (#22595098)
NPM is a lot more than the CLI. Even if you use yarn as the CLI you are still using npm for hosting and all the other parts that don't run on your computer. You can run your own npm repo, but hardly anyone does for all their dependencies (not talking about just caching here).

I'd wager most people who use yarn even installed it via the npm CLI.

Re:NPM Is Joining GitHub by hinkley on Monday March 16, 2020 @03:59PM (#22596919)
I mean yes, but no, but yes. For one, a lot of companies end up using Artifactory or similar, so npm is the source of truth but not the source of tarballs.

Didn't GitHub set up their own npm registry recently? Shots have been fired in this regard. Which, now that I type that out, makes me kinda wonder how amicable this purchase was...

It'd be such a shame if something bad were to happen to your lovely repository...

Re:NPM Is Joining GitHub by madeofpalk on Monday March 16, 2020 @01:36PM (#22595061)
I suspect you're still using the npm repository though? That's the actual 'valuable' thing that NPM (the company) makes.
Re:NPM Is Joining GitHub by Normal_gaussian on Monday March 16, 2020 @01:36PM (#22595054)
yarn v1+ or yarn v2/berry?

Switching to berry has been a huge PITA over here, but I don't want to give up workspaces

Re:NPM Is Joining GitHub by hinkley on Monday March 16, 2020 @02:52PM (#22596076)
Our 'workspace' is so ornate that yarn couldn't handle it. 1.21+ almost looks right, but something very bad is still going on with mocha deduping, such that tests are failing with really bizarre error messages.

I check yarn about every three months, or when I find a new, infuriating bug with the npm CLI (so, every couple of months on average). I think npm install suffers greatly from not having a formal spec. It has been bugfixed by so many different individuals now that it has reached a truly astounding level of schizophrenia.

If yarn didn't exist, I would have started trying to break down the install problem into many independent concerns that can be reasoned about individually and tried to solicit help in making a full installer out of it. If I'd known I'd still be trying to make yarn workspaces work for us 18 months later I probably would have.

Node modules in general have some bad patterns of delegation that are utterly antagonistic to self-documentation, and both yarn and npm seem to suffer from this as well. I think in the next week or so I'm going to have to set up a small test case that exhibits the yarn bug I'm seeing, or any of the half a dozen interlocking (emphasis on 'lock') npm bugs that now have me painted into a very tiny corner.

Re:NPM Is Joining GitHub by IsaacSchlueter on Monday March 16, 2020 @07:09PM (#22599265)
Your take on the installer in npm v6 is not wrong. It got that way by a process of gradual iterative evolution, and it has lots of warts.

npm v7 features a ground-up rewrite of the tree resolution and deification logic in the @npmcli/arborist module. I recommend checking it out, or at least staying tuned for the beta coming soon.

Re:NPM Is Joining GitHub by hinkley on Monday March 16, 2020 @03:30PM (#22596587)
> yarn v2/berry?

I had still been following 1.x

Looking at https://yarnpkg.com/advanced/migration : T-T

We have so many little modules from different teams, or even borderline abandonware, that it would take ages to make these changes, and 'yarn node'?? Just... no. How is that ever gonna work consistently with node_modules/.bin?

At this point my choices are, start contributing to yarn and npm development, or get my ass in gear on learning Elixir and Rust. I have been wondering for maybe 18 months if I might be 'done with Node'. I think I've had it backward this whole time. Node may in fact be done with me.

Re:NPM Is Joining GitHub by searchableguy on Monday March 16, 2020 @11:13PM (#22601262)
Yeah, yarnv2 is a BIG change and one that came out without much noise. There is no node_modules now by default. Pnp is forced (which was released in yarn as an experiment back in 2018 without much adoption).

I have been wondering the same thing. I left node for 8 months and I come back to see a lot of things have been abandoned in favor of yet another wheel implemented a bit differently. I wish changes were more visible and subtle. Rewriting seems like a plaque to js ecosystem except no one rewrites some really old unmaintained dependency we have hidden in every new shiny project.

Re:NPM Is Joining GitHub by ProAm on Monday March 16, 2020 @01:16PM (#22594763)
"Microsoft acquires npm"
Re:NPM Is Joining GitHub by Verdex on Monday March 16, 2020 @01:19PM (#22594804)
Yeah, I was confused when I first heard of it because it seems like an odd couple to "join" one another. However, it makes perfect sense for github to purchase npm.