Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Consider adding `npm dedupe` to project upgrade instructions

See original GitHub issue

When upgrading SPFx projects from one version to another, when you need to upgrade one or more npm packages, often you end up with a bunch of TS errors about duplicate incompatible types. I found out, that running npm dedupe after upgrading packages, solves this issue and prevents you from having to delete node_modules and the lock file. Should we consider adding npm dedupe to the set of upgrade instructions whenever we suggested upgrading one or more packages?

/cc: @baywet @wobba @VelinGeorgiev

Issue Analytics

State:
Created 5 years ago
Reactions:1
Comments:9 (6 by maintainers)

Top GitHub Comments

1reaction

waldekmastykarzcommented, Sep 21, 2018

Ideally, that would belong in the SPFx docs as it’s something that’s been coming up, and will be coming up in each SPFx version no matter if you’re creating a new project or upgrading an existing one.

1reaction

waldekmastykarzcommented, Sep 19, 2018

If we did it as an optional step, how would that be handled with the shortened command that you’ve added recently @baywet?

Top Results From Across the Web

Consider adding `npm dedupe` to project upgrade instructions

I found out, that running npm dedupe after upgrading packages, solves this issue and prevents you from having to delete node_modules and the ......

npm-dedupe

To prefer deduplication over novelty during the installation process, run npm install --prefer-dedupe or npm config set prefer-dedupe true . Arguments are ...

Npm-dedupe, npm-deprecate and npm-dis-tag CLI options

This command deprecates a version of a package. This CLI command updates the npm registry entry for a package, providing a deprecation warning ......

How to update dependencies of dependencies using npm

The common solution is to put it to package.json within devDependencies or dependencies with ^1.2.2 . I don't want to put it into...

npm packages in the Package Registry - GitLab Docs

Replace @scope with the root level group of the project you're installing to the package from. · Replace your_domain_name with your domain name,...