|
|
|
|
|
by mhio
1680 days ago
|
|
Not that I agree with the methodology running `corepack enable` introduces, providing OS shims for the specific package manager commands to download them... corepack (or package manager manager) was transferred to be a Node.js foundation project, voted to be included in release by the Node.js Technical Steering Committee. The one member I'm aware is affiliated with Github/NPM abstained from the vote. The specific utility of corepack is being championed by the package managers not distributed with node so that (Microsofts) `npm` is not the single default choice. I'm interested to hear what parts of this you see as coming from Microsoft/NPM as I didn't get that vibe? In my view this was more likely reactionary to the Microsoft acquisitions (npm previously being a benign tumour, doctors are now suggesting it may grow :) |
|
https://news.ycombinator.com/item?id=29250472
https://news.ycombinator.com/item?id=29249013