fand
commented
5 days ago Hi @gabrielatwell1987 ! Thx for report.
I created a sandbox with SvelteKit myself and I confirmed the issue.
I haven't figured out the correct way to solve this, but I found a workaround; add ssr.noExternal to your vite.config.ts.
// vite.config.ts
import { sveltekit } from '@sveltejs/kit/vite';
import { defineConfig } from 'vite';
export default defineConfig({
plugins: [sveltekit()],
ssr: {
noExternal: ['@vfx-js/core']
}
});Hope this will work on your side as well 🙏 I'll post an update once I fix the problem fundamentally.
(memo for myself)
The problem is that Node.js can't resolve relative imports without extensions from ESM modules.
import { foo } from "./foo.mjs"; // OK
import { foo } from "./foo.js"; // OK
import { foo } from "./foo"; // NGVFX-JS builds the output file using tsc, but tsc can't convert import statements to include the extension.
So we have 2 possible solutions:
- Add file extensions to imports with Babel etc
- Setting up a new tool just for this sounds a bit too much for me...
- Bundle the output file with Rollup etc
- This allows us to stlip all relative imports in VFX-JS
I didn't encounter this issue in docs-vfx-js probably because I use monorepo, but I'm not sure.
Nagitch
gabrielatwell1987
Every time I try to use this with the sveltekit framework, it always says that it can't find the @vfx-js/core module.. I'm guessing it has to do with SSR. How do you use this with SSR?