Chore: Update Dependencies #24
Conversation
There was a problem hiding this comment.
Left a few comments on quirks from manual updates. There's a tool called npm-check-updates which is much better at these types of things than NPM itself; I forgot to include in the issue but that's what I would recommend and it handles this well.
npx npm-check-updates --format group
npx npm-check-updates --upgrade --target minor --format group| "@types/node": "^20.8.3", | ||
| "@types/react": "^18.2.25", | ||
| "@types/react-dom": "^18.2.11", | ||
| "@types/node": "^20.8.9", |
There was a problem hiding this comment.
[Please Change]: Dependency versions in package.json are also included in package-lock.json - you need to run npm install after updating the versions here.
| "autoprefixer": "^10.4.16", | ||
| "eslint": "^8.51.0", | ||
| "eslint": "^8.52.0", | ||
| "eslint-config-airbnb": "^19.0.4", | ||
| "eslint-config-airbnb-typescript": "^17.1.0", | ||
| "eslint-config-next": "^13.5.4", |
There was a problem hiding this comment.
[Please Consider]: While the latest version of eslint-config-next (and next) is v14, there is a more recent v13.5.6 release which is available as well. In general it's good to update to latest minor prior to making the major jump.
This PR updates most dependencies to their latest versions. Outdated dependencies were found using
npm outdatedand they were updated withnpm updatewooo 🥳🥳.Resolves #20. A couple of dependencies w/ possible breaking changes like
nextandeslint-config-nextwill be updated in a separate PR :)