Configure --legacy-peer-deps with .npmrc #283
-
|
I'd love it if I could configure npm (globally and per project) with the Proposed config name: This could be in wherever |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments · 13 replies
-
|
@kentcdodds Hey Kent! This should already be possible with setting the |
Beta Was this translation helpful? Give feedback.
-
|
(note that lts/gallium describes node, being on a node version doesn't guarantee you're on any particular npm version) |
Beta Was this translation helpful? Give feedback.
-
|
Hi folks, sorry to be reviving an old thread. We use CI/CD to automatically deploy to feature environments and I just came across this after someone in our team installed a npm package locally with However, I'm not sure that I'm ok with just accepting all "legacy / unmaintained" packages moving forward and I'm curious to hear your approach on how to best manage our app integrity and package versions. Q1. Would it not make sense for --legacy-peer-deps to have some value (other than boolean) in order to formally allow certain packages through, but not all? Q2. is your preferred "best practice" to (a) always allow all updates (which will generally create some problems with packages not maintained regularly enough) or (b) lock all packages version and perform monthly or quarterly or yearly "upgrades" @darcyclarke curious to here your thoughts mate. Any reading material welcome. |
Beta Was this translation helpful? Give feedback.
-
|
In general, I'd suggest not allowing any dependency that requires the flag - since that means your dep graph is invalid. The only reliable way to keep your dep graph valid is to enforce that it remains so, by never using the legacy flag. |
Beta Was this translation helpful? Give feedback.
-
|
thank @ljharb -- am very much i agreement with that. It does mean however that any upgrades may yield packages that need to be replaced and/or wait until the maintainer also upgrades, right? The only way to avoid this would be for our team to
right? |
Beta Was this translation helpful? Give feedback.
-
|
Yes, exactly right. |
Beta Was this translation helpful? Give feedback.
-
|
I just ran the command |
Beta Was this translation helpful? Give feedback.
-
|
It should change |
Beta Was this translation helpful? Give feedback.
-
|
there's a ref: https://docs.npmjs.com/cli/v9/commands/npm-config#location |
Beta Was this translation helpful? Give feedback.
-
|
for some reason, NPM 9 ignored the project-level setting - in fact, it appears to ignore anything in the first line of |
Beta Was this translation helpful? Give feedback.
-
|
npm config set legacy-peer-deps true : what happens if I run this command |
Beta Was this translation helpful? Give feedback.
-
|
It will add |
Beta Was this translation helpful? Give feedback.
@kentcdodds Hey Kent! This should already be possible with setting the
legacy-peer-depsconfig (ref. https://docs.npmjs.com/cli/v7/using-npm/config#legacy-peer-deps). You can define it as a boolean in your local project or global.npmrcfile by runningnpm config set legacy-peer-deps truewith an optional-gto set it globally.