chore(deps): update Vite 7 #944
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Merged
Owner
Author
This stack of pull requests is managed by Graphite. Learn more about stacking. |
This was referenced Jun 12, 2025
hi-ogawa
force-pushed
the
06-12-chore_deps_vite_7
branch
from
cef6d0d to
96f8a16
Compare
hi-ogawa
changed the base branch from
06-12-chore_add_ecosystem-ci_script
to
graphite-base/944
hi-ogawa
force-pushed
the
06-12-chore_deps_vite_7
branch
from
96f8a16 to
4753171
Compare
hi-ogawa
force-pushed
the
06-12-chore_deps_vite_7
branch
from
4753171 to
a1dd0b5
Compare
hi-ogawa
force-pushed
the
06-12-chore_deps_vite_7
branch
from
a1dd0b5 to
1718157
Compare
hi-ogawa
changed the base branch from
graphite-base/944
to
06-17-chore_deps_update
hi-ogawa
force-pushed
the
06-12-chore_deps_vite_7
branch
from
1718157 to
23ea740
Compare
hi-ogawa
force-pushed
the
06-17-chore_deps_update
branch
from
bb3010f to
977ee1b
Compare
hi-ogawa
changed the base branch from
06-17-chore_deps_update
to
graphite-base/944
hi-ogawa
added a commit
that referenced
this pull request
Jun 17, 2025
Some change extracted from #944
hi-ogawa
force-pushed
the
graphite-base/944
branch
from
977ee1b to
92a1133
Compare
hi-ogawa
force-pushed
the
06-12-chore_deps_vite_7
branch
from
23ea740 to
e0b22cc
Compare
hi-ogawa
force-pushed
the
06-12-chore_deps_vite_7
branch
from
e0b22cc to
a638922
Compare
hi-ogawa
added a commit
to hi-ogawa/vite-plugin-glob-routes
that referenced
this pull request
Jun 19, 2025
Some change extracted from hi-ogawa/vite-plugins#944
hi-ogawa
force-pushed
the
06-12-chore_deps_vite_7
branch
2 times, most recently
from
2facd1d to
579f20e
Compare
Owner
Author
|
Hmm we actually need to wait |
hi-ogawa
force-pushed
the
06-12-chore_deps_vite_7
branch
from
1f97425 to
dfe61ea
Compare
hi-ogawa
force-pushed
the
06-12-chore_deps_vite_7
branch
from
ac3d273 to
7cd6de3
Compare
This was referenced Jul 2, 2025
Merged
Closed
Closed
hi-ogawa
force-pushed
the
graphite-base/944
branch
from
582de3e to
9c3f6f4
Compare
hi-ogawa
force-pushed
the
06-12-chore_deps_vite_7
branch
from
7cd6de3 to
4e1d60a
Compare
hi-ogawa
force-pushed
the
06-12-chore_deps_vite_7
branch
from
4e1d60a to
a37f06f
Compare
hi-ogawa
force-pushed
the
06-12-chore_deps_vite_7
branch
from
a37f06f to
ed0fb33
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The failures are due to
this.environmentinhotUpdatefor Vite 7 compatibility antfu-collective/vite-plugin-inspect#150@cloudflare/vite-plugin__vite_ssr_exportName__ is not definedwhy 🤔Oh, this is because
@cloudflare/vite-pluginbundlesvite/module-runnerand that doesn't have__vite_ssr_exportName__provided inrunInlinedModulecontext.Can we suggest to unbundle
vite/module-runnerand provide as separate module on runtime? https://github.com/hi-ogawa/vite-environment-examples/blob/c54e8e3b1ba0195677bb838d6f12be6510dc361d/packages/workerd/src/plugin.ts#L113-L117Expected resolvedPluginConfig to be definedthis seems same as ecosystem ci failure. We should fix it though.