prefresh/vite: runtimeCode is not defined
See original GitHub issueWhile working on a project of mine bundled with Vite using the preact preset, I’ve encountered strange errors which seemed to be from prefresh/vite.
Upon closer inspection of the error message and the lib’s code, I’ve found that in the vite/src/index.js file, line 24 there is indeed a reference to a runtimeCode
variable, which indeed is not define anywhere, leading to an unpleasant error 😦
Issue Analytics
- State:
- Created 2 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
Uncaught ReferenceError: process is not defined · Issue #1973
Describe the bug When I upgrade vite to any version after 2.0.0-beta.62 I get ... App.vue:36 Uncaught ReferenceError: process is not defined
Read more >vite uncaught referenceerror: require is not defined - You.com
Vite / Vue 3 : "require is not defined" when using image source as props ... There should never be require in source...
Read more >Troubleshooting - Vite
Vite cannot handle and does not support code that only runs on non-strict mode (sloppy mode). This is because Vite uses ESM and...
Read more >@vitejs/plugin-react - npm
The all-in-one Vite plugin for React projects. enable Fast Refresh in development; use the automatic JSX runtime; avoid manual import React in ....
Read more >Asset Bundling (Vite) - The PHP Framework For Web Artisans
However, it lacks some features that Laravel Mix supports, such as the ability to copy arbitrary assets into the build that are not...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Oh waw, that is completely my mistake 😅 fix incoming!
Thank you so much for looking into this @cyyynthia and for the in-depth explanation. This is much appreciated