fix "emitProgress is not defined" error, when run in-browser #3
Open
scipilot wants to merge 1 commit intohash-bang:masterfrom
Open
fix "emitProgress is not defined" error, when run in-browser #3scipilot wants to merge 1 commit intohash-bang:masterfrom
scipilot wants to merge 1 commit intohash-bang:masterfrom
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
in a strict mode build of a Vite/Vue/TS app, I get the error
index.js:197 Uncaught ReferenceError: emitProgress is not defined at Object.parse (index.js:197:3)as it seems this is the only variable without a definition.I tried various hacks like defining it globally in the Vite config, but this only solved it in dev, not a production build.
This only came up in a recent new project, so I can only assume its some new strict-mode behaviour.