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

⬆️ Upgrade to Vite 6 #758

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Conversation

sergei-maertens
Copy link
Member

Released a couple of weeks ago :)

Copy link

codecov bot commented Dec 20, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 80.02%. Comparing base (2973318) to head (d5c38bb).

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #758      +/-   ##
==========================================
- Coverage   80.05%   80.02%   -0.03%     
==========================================
  Files         238      238              
  Lines        4953     4951       -2     
  Branches     1350     1341       -9     
==========================================
- Hits         3965     3962       -3     
- Misses        958      959       +1     
  Partials       30       30              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@sergei-maertens
Copy link
Member Author

Blocked by storybookjs/storybook#29719 :)

@sergei-maertens sergei-maertens marked this pull request as draft December 20, 2024 09:01
Released a couple of weeks ago :)

This currently requires us to force storybook vite builder to
resolve esbuild to 0.24.0, despite vite 6.0.5 pinning this
dependency. See storybookjs/storybook#30115
@sergei-maertens
Copy link
Member Author

Workaround applied from pinned Storybook issue.

@sergei-maertens sergei-maertens marked this pull request as ready for review December 21, 2024 14:02
@sergei-maertens
Copy link
Member Author

@robinmolen @vaszig considering this is build tooling and CI is passing, I think it's not too extreme to merge this in main before the 2.5.0 release, but feel free to disagree if you think it's too risky!

Copy link
Contributor

@vaszig vaszig left a comment

Choose a reason for hiding this comment

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

I am not familiar with this, especially the new version, but if Robin agrees of course we can merge it!

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