-
-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Error when evaluating SSR module (Unexpected token 'export') in DEV #2914
Comments
I created a skeleton app and run in dev but I'm not getting the errors. Please provide a reproduction so we can track this down. Thanks! |
Sorry, it was my mistake. But the reason of this error output totally unclear. I've just put image with wrong path (missed file): So, it's really strange error output. And there is even no file where I'm put this missed image. Totally confused 🤷♂️ |
Having the same types of issues here. Valid Vite imports of functions in my .ts files are just failing. Seems really random. |
Without a proper reproduction there is nothing we can do to analyze this further. Please provide the required information. |
@dominikg I have similar case here: https://stackblitz.com/edit/sveltekit-oydoc5?file=src/lib/Chart.svelte when used with |
The issue in the reproduction is caused by It can be worked around by including it in Vite's processing: // svelte.config.js
export default {
kit: {
vite: {
ssr: {
noExternal: ['echarts']
}
}
}
}; No idea what's going on with the original issue but since there's no repro there's no way for us to investigate — closing. |
This workaround isn't working anymore after the switch to Vite 3, reproduction in https://github.com/csjh/broken_kit Edit: fixed by putting |
Describe the bug
When I run
pnpm run dev
and load some page I've got an error in console:But if I reload the page — no more errors until I again restart dev.
Reproduction
I can't tell exaclty why and when in happens, but looks like it's an error from packages. Probably after updating dependencies few days ago.
System Info
Severity
serious, but I can work around it
Additional Information
No response
The text was updated successfully, but these errors were encountered: