`[vite] Error when evaluating SSR module`, `SyntaxError: Unexpected token '.'`
See original GitHub issueFollow up of https://github.com/brillout/vite-plugin-ssr/issues/93#issuecomment-860040841.
Does rm -r ./node_modules/.vite/
get rid of the error?
I couldn’t reproduce with following steps.
1. Run `yarn create vite-plugin-ssr`
2. Select `react-ts`
3. `cd vite-project`
4. Move pages to ./src/pages
5. `yarn install`
6. Run `yarn dev`
7. Open http://localhost:3000/
Issue Analytics
- State:
- Created 2 years ago
- Comments:14 (8 by maintainers)
Top Results From Across the Web
"[vite] Error when evaluating SSR module" when using ssh2 ...
I am trying to build a server management GUI with SvelteKit using SSH via ssh2-promise . The strange thing is: the file /Users/user/evaluating- ......
Read more >Shopify Hydrogen Demo Site Error - SyntaxError: Unexpected ...
I set me up a new site using the demo site for shopify hydrogen as a template, when i try and run it...
Read more >How to Fix „Uncaught SyntaxError: Unexpected token 'export
Using type="module" on the <script> tag solved the „Unexpected token export ” error. The browser runs the imported JavaScript without issues.
Read more >Configuring Vite
When running vite from the command line, Vite will automatically try to resolve a config file named vite.config.js inside project root. ... Note...
Read more >How To Fix Unexpected token u in JSON at position 0 - Isotropic
This error is caused when you are attempting to parse a non-existent property. Typically, this is due to a misspelling, or simply referencing ......
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 FreeTop 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
Top GitHub Comments
At least we are making some slight progress in elucidating this 😅
Seems like a bug on Vite’s or Node.js’s side. Anyways good to know; thanks for reporting back.