Skip to content

Commit

Permalink
Do e013cc0’s typescript-eslint version bumps in package.json
Browse files Browse the repository at this point in the history
So that they don’t get lost next time we need to do something that may
cause information in package-lock.json to get discarded, for example
resolving a merge conflict.

I asked whether my approach in e013cc0 was incorrect, and Owen said he
thought it was: "i'm pretty sure what you're supposed to do is put
anything you want to control the version of into package.json", so let’s
do that.
  • Loading branch information
lawrence-forooghian committed Nov 8, 2023
1 parent 8dbfcc7 commit 89edf04
Show file tree
Hide file tree
Showing 2 changed files with 4 additions and 4 deletions.
4 changes: 2 additions & 2 deletions package-lock.json

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

4 changes: 2 additions & 2 deletions package.json
Original file line number Diff line number Diff line change
Expand Up @@ -45,8 +45,8 @@
"@types/node": "^18.0.0",
"@types/request": "^2.48.7",
"@types/ws": "^8.2.0",
"@typescript-eslint/eslint-plugin": "^5.14.0",
"@typescript-eslint/parser": "^5.14.0",
"@typescript-eslint/eslint-plugin": "^5.59.6",
"@typescript-eslint/parser": "^5.59.6",
"@vitejs/plugin-react": "^1.3.2",
"async": "ably-forks/async#requirejs",
"aws-sdk": "^2.1413.0",
Expand Down

0 comments on commit 89edf04

Please sign in to comment.