Kristoffer K.
Kristoffer K.
Just to note: if you're using Yarn 2 you can already do this using the `link:` protocol https://yarnpkg.com/features/protocols https://yarnpkg.com/features/protocols#why-is-the-link-protocol-recommended-over-aliases-for-path-mapping
Since this is labled `esm` could someone ping the `@nodejs/modules` team so we can get a clarification about what the expected behaviour is supposed to be?
> We can use the same logic as in webpack I would advise against that as you now end up with another cache folder since not all tools will follow...
@sosukesuzuki I would just stick to `node_modules/.cache/prettier` regardless of the package manager and its install strategy.
> If people have other files I should test on please let me know Here is a 10MB file from a Go project and a 20MB file from a Rust...
While it isn't what you're asking for, you could populate the cache before it becomes readonly: ```Dockerfile FROM node:18-bullseye RUN corepack enable yarn && yarn -v ``` Though ideally you...
As the npm error tells you, it refuses to overwrite something it didn't create, you can add the `-f` flag to force it. ```sh npm -g -f install [email protected] ```
> actually, you can just check for .yarn/cache directory No, don't do that as it can be custimized and might not exist, check the `yarn.lock` file for `__metadata:` instead
Moved this to classic since v3.2.2 doesn't advertise nor support a `help ` command.
The npm registry says the package was modified at `2021-12-08T22:36:21.996Z` https://registry.npmjs.com/benchmark, though perhaps we should show when the version was published instead.