Skip to content
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

chore: update stale packages #3057

Merged
merged 2 commits into from
Nov 25, 2024
Merged

chore: update stale packages #3057

merged 2 commits into from
Nov 25, 2024

Conversation

tracy-french
Copy link
Contributor

@tracy-french tracy-french commented Nov 21, 2024

Overview

All over the code base, the wrong versions of dependencies are being used. This change fixes this issue, allowing the dependency versions listed in package.json files to be used correctly.

The issue was likely caused by improper installation of packages using npm workspaces. I plan on talking with the team how to install packages.

In the process of fixing this issue, which was primarily fixed by regenerating package-lock.json, the updates up many dependencies had to be handled, most notably storybook. There was a version mismatch between doc-site (storybook v7) and other packages (storybook v6) and only the lock file was holding the issue at bay. Once unlocked, transitive dependencies experienced versioning conflicts.

In handling the storybook issue, I figured we might as well upgrade all the way to storybook 8 with vite. Hope you enjoy the dev experience!

Overall, as a result of this change, we should see:

  • Less bugs related to version issues, especially differing between machines.
  • Significantly faster installs (2-4 times faster)
  • ~80% of vulnerable packages updated (90 -> 16 on my machine)
  • Faster development env using vite instead of webpack with storybook
  • ~1-2 minutes removed from GH action playwright tests with vite storybook startup

Legal

This project is available under the Apache 2.0 License.

@tracy-french tracy-french force-pushed the force-update-packages branch 14 times, most recently from 45c0e26 to f6d986f Compare November 24, 2024 20:14
@tracy-french tracy-french marked this pull request as ready for review November 25, 2024 00:47
@tracy-french tracy-french force-pushed the force-update-packages branch 8 times, most recently from 31a50c6 to ea05f43 Compare November 25, 2024 18:16
@tracy-french tracy-french changed the title chore: force update packages chore: update stale packages Nov 25, 2024
"test:ui:update": "npm run playwright -- npx playwright test --update-snapshots",
"test:ui:dev": "npx playwright test --ui",
"storybook": "npm run copy-assets:es && start-storybook -h 0.0.0.0 -p 7006",
"test:ui:update2": "npm run playwright -- npx playwright test --update-snapshots",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: did you mean to change the command name here?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oof. That was a mistake. I'll fix it!

@hwandersman
Copy link
Contributor

Anything to add to the package READMEs about new commands, installation, storybook setup, env vars?

@tracy-french tracy-french merged commit 833f3e7 into rc Nov 25, 2024
18 checks passed
@tracy-french tracy-french deleted the force-update-packages branch November 25, 2024 19:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants