Repository navigation
Bump Axios 1.19 to 1.20 #199
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -9,7 +9,7 @@ | |
| "@types/react": "^18.2.0", | ||
| "@types/react-dom": "^18.2.0", | ||
| "@vitejs/plugin-react-swc": "^3.7.2", | ||
| "axios": "^1.19.0", | ||
| "axios": "^1.20.0", | ||
| "js-yaml": "^4.3.2", | ||
| "micromatch": "4.0.8", | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I seem to be getting an exit 100 error when trying to do docker compose up - might be good to huddle to see why - seems like it's occurring for me in the get-apt-update step of the docker file in server directory. Having @bwang-icf try to get another data point
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I'm able to get this spun up and working as is
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Idk I keep getting an error - will bring it up at eng sync. @bwang-icf can take over the review - I would just verify the latest version update of axios 1.20.0 is in the container and the lock files are committed. |
||
| "process": "^0.11.10", | ||
|
|
||
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We'll need to ensure that we commit package-lock.json AND yarn.lock as well so us developers don't have to run npm i or yarn install and can just use the latest lock file version.