Steven

Checking in here again. I can say that all outstanding issues are complete and everyone who tries out corepack is very happy with it. Its solving real problems. For example,...

I wouldn't consider signing releases a blocker to going stable. It would be a nice feature though. Correct me if I'm wrong, but I don't think `npm i -g [email protected]`...

This issue needs to be fixed before going stable: - #195

It sounds like the path forward here is to create a [npm RFC](https://github.com/npm/rfcs/issues/new) for the `run` shorthand that yarn supports ([mentioned above](https://github.com/nodejs/corepack/issues/57#issuecomment-925733698)). Are there any yarn docs that the npm...

I must have missed that above! I tried `$npm_execpath` with the example above and it works today 🤩 ```json { "scripts": { "compile": "echo 'compile done'", "download": "echo 'download done'",...

Oh no, I just realized that `$npm_execpath` doesn't work on Windows 🤦 That explains why no one would use it for `postinstall`.

I see. Then consider this a feature request to change it to the repo's default branch 🙂 Also note that GitHub is going to be changing the default branch for...

I think that's fair. Maybe have two commands for each solution. ## Copy a file ### Novice ``` cp readme.txt documents/ ``` ### Expert ``` cp --verbose --no-clobber --no-dereference --target-directory='documents'...

How about `new URL('./asset.txt', import.meta.url)` which is supported by [`@vercel/nft`](https://github.com/vercel/nft/blob/main/test/unit/import-meta-url/input.js) and other static analysis tools?

@amio That's what it sounds like. Maybe they blocked the Vercel IP in IAD for some reason? The IP address is not static so its strange to see this happening...