Update Project Dependencies
Update Project Dependencies
Updating the dependencies is a tedious job. This doc is intended to help streamline the process and make it painless.
Maintain Update Log
There's a sample Update Log
at the end of this document. Create a new file where you can dump the Version Diff, Test results, Chrome/Node/npm versions. Mention the dependencies that you had to roll back along with the reason. Optionally you can mention the errors/warnings that you encountered while updating dependencies.
Managing Node Versions
It is recommended that you use Node Version Manager or Node Version Control to switch node versions quickly in order to run and test this project on multiple node versions.
Update Tooling
Update npm:
- Run
npm install -g npm
- Run
npm -v
and record npm version inUpdate Log
.
Update Chrome
Download the latest version or go to chrome://settings/ and update.
Go to
Chrome -> About
and record version number inUpdate Log
Update Dependencies
npm-check-updates is a great tool to update your dependencies. It will only update your package.json
. Run npm install
if you want to install updated package versions. There are 3 useful commands.
ncu -u --semverLevel minor
ncu -u --semverLevel major
ncu -u
Confirm/adjust eslint-config-airbnb compatible dependency versions
npm info "eslint-config-airbnb@latest" peerDependencies
Pinned Version Numbers
react-boilerplate
does not use "^", "~", etc., and these should be removed from package.json
, if present. See #598 for more details.
At this point, you should copy and paste the version diff from the terminal into your Update Log
.
Correct Errors and Rollback Dependencies
Run npm install
to install updated versions and then start the example app by running npm start
. Make sure that the project is running smoothly. If not, track down the dependencies that are causing problems and try to roll them back one by one and check if the example application is running.
Note down the rolled back dependencies and state the reason in your Update Log
.
Full Regression Testing
Most of the errors/warnings would go away once you roll back the problemetic dependencies. But we need to make sure that the internal commands, tools, scaffolding etc. are functional too.
Example App:
rm -rf node_modules && rm package-lock.json
npm install && npm start
Browse example app on development server
- Browse Features page, change language to
de
- Browse NotFound page
- Browse Features page, change language to
Browse example app on dev tunnel
Browse example app on Production server
Browse example app offline
Identify problems that occur and try to resolve them by rolling back the respective dependencies. Update the Update Log
.
Internal Commands:
npm run clean
(Be careful, this will commit all your changes.)npm run generate component
TestComp /w defaultsnpm run generate container
TestPage /w defaults- Add a new route in the App container:
- Use TestComp on TestPage -> bypass all tests in TestComp and TestPage (set true = true)
npm start
>localhost:3000/test
npm test
(expect test failure due to incomplete test coverage)npm run build
npm run start:prod
>localhost:3000/test
Sample Update Log
Tooling Versions
- Node 8.11.4
- npm 6.4.0
- Mac OS 10.13.6
- Chrome 68.0.3440.106 (64-bit)
:spiral_notepad: Notes
react-router
was not updated. Thanks to @anuraaga for all his work. Ref- #1746history
was not updated because ofreact-router v3
's dependency on it. Should go away when #1746 is merged.react-test-renderer
was added as a dev-dependency because enzyme was showing warnings-A few deprecation warnings were added in React 15.5. This supports the new APIs that React recommends. Ref. #876
- If you see a package-name being repeated, note that the version number of the last occurrence will get precedence.
π¦ Version Diff
[0] PATCH UPDATES
[1] MINOR UPDATES
[3] MAJOR UPDATES
[4] ROLLBACKS
[5] NEW DEPENDENCIES
Errors Encountered
Incompatible per
npm info "eslint-config-airbnb@latest" peerDependencies
adjust eslint-config-airbnb compatible dependency versions. see: https://www.npmjs.com/package/eslint-config-airbnbeslint 3.13.1 β 3.15.0 <--- rolled back
Error observed in Travis CI build
history
Incompatiblereact-boilerplate@3.4.0 /Users/glen/Documents/JavaScript/Research/react-bp βββ UNMET PEER DEPENDENCY history@4.5.1
npm ERR! peer dep missing: history@^2.0.0 || ^3.0.0, required by react-router-scroll@0.4.1
history 3.2.1 β 4.5.1 <--- rolled back
Addressed here https://github.com/imagemin/imagemin-pngquant/issues/32 Needs Testing
Error: (some OS X installations only, not version specific)
Addressed here https://github.com/imagemin/imagemin-pngquant/issues/32, but throws warnings (below)
In ./app/components/Header/banner.jpg Module build failed: Error: dyld: Library not loaded: /usr/local/opt/libpng/lib/libpng16.16.dylib Referenced from: ~/react-boilerplate/node_modules/mozjpeg/vendor/cjpeg Reason: image not found
image-webpack-loader 2.0.0 β 3.0.0 <--- rolled back see: https://github.com/mxstbr/react-boilerplate/pull/1322#issuecomment-266264527 and #1335
Warning: Observed on
npm start
WARNING in ./app/components/Header/banner.jpg DEPRECATED. Configure gifsicle's interlaced option in it's own options. (gifsicle.interlaced) @ ./app/components/Header/index.js 47:0-34 @ ./app/containers/App/index.js @ ./app/app.js @ multi eventsource-polyfill webpack-hot-middleware/client?reload=true ./app/app.js WARNING in ./app/components/Header/banner.jpg DEPRECATED. Configure optipng's optimizationLevel option in it's own options. (optipng.optimizationLevel) @ ./app/components/Header/index.js 47:0-34 @ ./app/containers/App/index.js @ ./app/app.js @ multi eventsource-polyfill webpack-hot-middleware/client?reload=true ./app/app.js
image-webpack-loader 2.0.0 β 3.2.0 <--- Rolled back