Antoine du Hamel
Antoine du Hamel
Hello, we've introduced the native UI integration with Uppy 3.x (so now the mirroring is dealt with by the client's OS), can you confirm this has resolved the issue?
@boneskull The restriction only applies to the `package.json` ad hoc field, you can still do e.g. `corepack [email protected] install`, does that cover your use case?
@boneskull are you using an old version of Corepack maybe? For me, running `COREPACK_ENABLE_PROJECT_SPEC=0 corepack npm@7 --version` works and returns `7.20.1`.
I for one am not aware of it, do you have a link to a discussion that explains what's the issue?
> I would hope to see checksum verification as mandatory prior to moving ahead. I don't think that can ever happen, we would need to have a trusted source for...
> * making it clear package managers in corepack and tools still use the npm registry by default I don't think we can guarantee that, and also I think package...
Sigstore seems to be npm package specific, I'm not sure if it would work well for us 🤔 I was thinking on what would be a generic solution, and maybe...
Isn't it because of https://github.com/nodejs/build/pull/3598?
There are two things that come to mind: - how to make `registerLoader` happen (what the final API should look like, and what are the steps (ideally each step should...
Yes, my PR goal is to run the code is a CJS-like environment when the `load` step returns `{ format: 'commonjs', source: … }`.