node_modules in server side? #571
Replies: 2 comments 11 replies
-
What's the full stack trace? |
Beta Was this translation helpful? Give feedback.
-
|
@brillout, I also ran into this same error when I tried to use this the examples/redux template with a specific 3rd-party package. (In my case the 3rd-party package is react-live-runner, which seems to have all the modern JS exports set-up, but still throws this error.) I wrote a question on StackOverflow before I found this discussion, and that has a bunch of details. In my case, the full error is: I split the examples/redux code into a repo and added the package that's causing problems here: https://github.com/antun/vite-ssr-redux-react-live-runner-example |
Beta Was this translation helpful? Give feedback.
-
|
(Reproduction with pnpm for further reference: https://github.com/brillout/vite-ssr-redux-react-live-runner-example.) |
Beta Was this translation helpful? Give feedback.
-
|
What is it that -- UPDATE: I tried switching to
... and:
my Do people typically have to exclude these? Things like -- Also in my simple text case, I'm still somewhat stuck because while using Previously I was able to run |
Beta Was this translation helpful? Give feedback.
-
|
Ah, that's very helpful - thanks! Just posting some notes here in case someone else runs into this. After adding the debugging code to the React code, I'd get output like this: Then I searched node_modules for references to that element, e.g. I'm still dealing with another different error now:
I do see that one has a couple of other workarounds listed on https://vite-plugin-ssr.com/broken-npm-package, and I'll try those. (The |
Beta Was this translation helpful? Give feedback.
-
Yes, that isn't unusual. A lot of packages ship invalid code. That's very unfortunate and to fix the situation changes are needed that are outside the realm of VPS. The relevant entities are relunctant/slow to change, so it'll take some time until we iron this out.
I'd recommend to do the following instead. A typical log will look like this:
Go to the position // Line 127, column 12:
/*...*/ createElement(someVar, /* ... */)
You can temporarily fix the problem by replacing To permanently fix the problem: go to where (FYI this is the biggest problem currently with Vite/VPS (the only one actually...). I care a lot about fixing the situation but it's going to take some time. In the meantime, doing some manually digging like we're doing here should work, but if it doesn't then definitely let me know.) |
Beta Was this translation helpful? Give feedback.
-
|
Actually, if you set There is still manual work to do though. Everytime you hit:
Then add to the package // vite.config.js
import { cjsInterop } from 'vite-plugin-cjs-interop'
export default {
plugins: [
cjsInterop({
// List of dependencies that require interop
dependencies: [
'some-npm-package'
]
})
]
}(FYI, I think we can make Let me know how much |
Beta Was this translation helpful? Give feedback.
-
I am using https://github.com/brillout/vite-plugin-ssr/tree/main/examples/react-router/
And I get a lot of
Cannot use import statement outside a modulewhen importingnode_modules/*/*.jsfiles to server. I guess it's because node.js runtime run the raw file ofimport xxxinstead of the transpiledrequire(xxx)After hacking
type="module"in the package.json of those node_modules it works. But it's annoying, since the deps are deeply nested and I constantly get these errors.My question
type="module"?import xxxand what should I do? Should I add some transpilation to server files?Beta Was this translation helpful? Give feedback.
All reactions