-
Notifications
You must be signed in to change notification settings - Fork 16
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
When using with Vite 4.3.4 and newer plugin breaks #289
Comments
Hi! I tried to reproduce but no luck here (tried on vite 4.3.4 and 4.3.5) :( |
I'm having the same problem here, when upgrading from 4.3.3 to 4.3.5. The problem is fixed when I disable this plugin. This is what (the relevant part of) my vite config looks like:
The list of my dependencies:
|
@ikenfin Hi! Log:
VITE_PLUGIN_SENTRY_CONFIG value leads to a parse error. Temporary fix: const { config, ...vps } = vitePluginSentry({ ... })
export default defineConfig({
plugins: [
vps,
],
}); |
@WouterSioen @Kretiss @Eazymov Hi! It seems that this encoding appears only when you use I've done some experiments and it seems that // main.tsx
// fails
const {
VITE_PLUGIN_SENTRY_CONFIG
} = import.meta.env
console.log(VITE_PLUGIN_SENTRY_CONFIG.dist)
// works
console.log(import.meta.env.VITE_PLUGIN_SENTRY_CONFIG.dist) Can you plz check how you are using import.meta.env in your code and replace it with full property path to check is that works? |
In my
This thus does use the full property path |
I think this is an issue in vite and how it handles |
Looks like this is fixed with the release of vite 4.4.8, I cannot reproduce the problem anymore after updating 🙌 |
Hey, I am experiencing weird error and I really dont know from where it comes from. Everythink works fine with Vite version 3.4.3 and lower, but from version 3.4.4 it always throws error at the end of the build, right after source maps list.
Here is printscreen of that error:
Remove of plugin in vite.config.ts fixes this issue.
Does anyone know what could be the solution here? Thanks!
Here is dependencies list
And plugin setup:
The text was updated successfully, but these errors were encountered: