Repository navigation
fix(build): add workaround for building on stackblitz - #22840
Merged
Merged
Conversation
sapphi-red
commented
Jul 9, 2026
commented
Jul 9, 2026
@vitejs/plugin-legacy
vite
commit: |
This was referenced Oct 22, 2026
[Historical PR] deps(npm): bump vite from 8.1.3 to 8.1.4 in /web/client
rennerdo30/bifrost-proxy#187
Closed
[Historical PR] deps(npm): bump vite from 8.1.3 to 8.1.4 in /web/server
rennerdo30/bifrost-proxy#188
Closed
[Historical PR] deps(npm): bump vite from 8.1.3 to 8.1.5 in /web/client
rennerdo30/bifrost-proxy#195
Closed
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
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.
When building on stackblitz, the
import.meta.resolvein the output was replaced with a slightly different value (𝐢𝐦𝐩𝐨𝐫𝐭.meta.resolve).https://stackblitz.com/edit/vitejs-vite-yuazbcvz?file=index.html&terminal=build
This causes
ReferenceError: 𝐢𝐦𝐩𝐨𝐫𝐭 is not definederror.This is caused by how stackblitz works and the way we use
function.toString(): https://stackblitz.com/edit/node-vqfvv8dy?file=index.jsThis PR adds a workaround for that.