SSR Mode Fails on Deploy When Importing Nested Files Inside Node Module #12424
Unanswered
1b4Pi
asked this question in
CLI - SSR mode
Replies: 1 comment
-
|
just for test: Try |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I've got a Quasar SSR/PWA handoff web app that crashes on the server with the catch-all 500 error as soon as I try to import js files bundled within an installed node_module dependency.
Everything works fine in both dev env (spa) and prod env (ssr) when using deps from:
import { Vector2 } from "three";But prod fails when trying to:
import { EffectComposer } from "three/examples/jsm/postprocessing/EffectComposer";I tried including the js file in my boot config:
boot: [ "i18n", "axios", ... "~three/examples/jsm/postprocessing/EffectComposer", ],That didn't resolve the issue on its own. I feel like I'm missing a step here but it's not clear in the docs.
I also tried importing from a boot file (properly?):
src/boot/composer.js:
quasar.conf.js:
boot: [ "i18n", "axios", ... "composer", ],And finally the Vue file:
import { EffectComposer } from "../../../../boot/composer";While everything is fine in SPA dev land. Server-side this is what I'm getting on the logs:
Because I'm working with scripts that use WebGL, I thought maybe that was the issue and went down a wild path of finding a VPS that offers Ubuntu20x with NVIDIA GPU support. While it was fun spinning that server up... alas, that damn 500 error still showed on deployment with both the GPU and CPU servers.
Any pointers as to what I'm doing wrong or missing? Many thanks. Quasar is very, very, rad.
Beta Was this translation helpful? Give feedback.
All reactions