Am I the only one that hates the decision to no longer support corepack?
It is node.js core that decided to drop corepack, now both yarn and pnpm are build own version of that.
Pnpm 12.0
61–70 of 72 posts
Re: Pnpm 12.0
#62Earlier quoted context omitted.
Perhaps – but it's a useful grammatical construct in everyday use, handy for structuring sentences. And with the prevalence of AI, it rubs off on the smelly humans, who also find it useful and use it more as a result. (I used an en dash here instead of an em one – also valid, easier to type, and shorter).
Nah. I NEVER say the dash pre-AI, at least in commoners writings. Maybe in some books etc. The dash you read today is 99.9% AI generated.
I've used it extensively in English due to learning the language through a lot of older books - but I've never bothered to actually pull out the emdash, I would hope people can see that I'm not trying to subtract one sentence from the other.
Re: Pnpm 12.0
#63I got to the conclusion that boring is good enough, for me NPM is the best tool, is not that fast, but the installation speed is not that bad, considering how many times I need to run from scratch, the difference does not matter, it is stable and it's the default Node package manager, so I don't need to bother to install in CI any other tool, etc. My experience for long living projects is to stick with the defaults,…
yeah the problem is npm is now Microsoft, just like Github. I trust Node. I don't trust NPM.
Re: Pnpm 12.0
#64I’m going to write a filter to remove comments that are just bitching about whether something is AI written or not. Seeing “slop” now starts to give me m$ vibes
> Short-term AI/GPT/LLM consulting services to help you strategize, discuss, and navigate the rapidly evolving world of artificial intelligence.
Re: Pnpm 12.0
#65Am I the only one that hates the decision to no longer support corepack?
I migrated a Node 24 repo to pnpm 12 and it works absolutely fine with corepack out of the box.
Re: Pnpm 12.0
#66They should focus on the tool, do not try to rewrite it… everyone tries to rewrite things to rust now, pnpm was already great alternative to npm - just keep improving it instead of rewriting:/
Re: Pnpm 12.0
#67Re: Pnpm 12.0
#68Re: Pnpm 12.0
#69I’m going to write a filter to remove comments that are just bitching about whether something is AI written or not. Seeing “slop” now starts to give me m$ vibes
> Short-term AI/GPT/LLM consulting services to help you strategize, discuss, and navigate the rapidly evolving world of artificial intelligence.
Drop me an email if you’re after a quote.
Re: Pnpm 12.0
#70Earlier quoted context omitted.
What’s the problem with that? Seems to make sense to me with the example and it’s important to point out. I’d expect an llm to explain in more detail to be honest.
It doesn’t quite make sense at face value by itself. It’s too condensed and takes some effort to parse out what it’s actually getting at. It’s not communicating why the change was made. It’s just a shiny way of saying the words without actually helping me easily understand what’s happening, what’s changing, why, etc. In plain English, maybe it’d be more like “Package specifiers for git repositories should no longer i…
They can include the protocol, it’s that regardless of what’s put in there it’ll use https, which is explained with examples both in the following sentences and then in more detail in a linked doc.
> For repositories on GitHub, GitLab, and Bitbucket, a specifier now names a repository rather than choosing a transport. github:owner/repo, owner/repo, git+https://…, and git+ssh://git@… all resolve through the host's canonical HTTPS URL, and the lockfile never records an SSH URL for those hosts. To reach a private hosted repository over SSH, configure the machine with git's own URL rewriting:
git config --global url."git@github.com:".insteadOf https://github.com/