Skip to content

Commit 8d7d309

Browse files
andrewconnellVesaJuvonen
authored andcommitted
add extra details about deleting node_modules (SharePoint#3724)
- after updating a package dependency, sometimes it's best to delete node_modules - added step recommending this - closes SharePoint#1561
1 parent 543fbd0 commit 8d7d309

File tree

1 file changed

+6
-0
lines changed

1 file changed

+6
-0
lines changed

docs/spfx/toolchain/update-latest-packages.md

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -78,6 +78,12 @@ After the packages are installed, execute the following command to clean up any
7878
gulp clean
7979
```
8080

81+
Furthermore, it is recommended to delete all old packages by deleting the **node_modules** folder and download (ie: reinstall) all dependencies with the updated package.json. Without this step, old versions may conflict with the newer versions the next time you build the project.
82+
83+
```sh
84+
npm install
85+
```
86+
8187
## Update your code
8288

8389
Depending on breaking API changes, you may have to update your existing project code and config files. For each release, the [release notes](https://aka.ms/spfx-release-notes) highlight any such breaking changes and the modifications required to your existing code. You must make sure you update your code with those fixes.

0 commit comments

Comments
 (0)