-
-
Notifications
You must be signed in to change notification settings - Fork 34
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] No loader is configured for ".node" files #74
Comments
Apparently a better alternative to excluding oslo is to exclude the actual offending dependencies.
|
This appears to have been caused by the latest release of ref (Oslo Discord): https://discord.com/channels/1004048134218981416/1239596097752793221/1240675071203344505 |
Another related issue: vitejs/vite#12989 |
+1 having the same issue |
Unfortunately there's little Oslo can do here so the fix is to just exclude |
Apparently this still does not work, or am I doing something wrong? I use SST ION (V3). Just setup the basics following the docs. Added to my existing sveltekit app. My vite.config.ts: import { sveltekit } from '@sveltejs/kit/vite';
import { defineConfig } from 'vitest/config';
export default defineConfig({
plugins: [sveltekit()],
optimizeDeps: {
exclude: ['@node-rs/argon2', '@node-rs/bcrypt']
},
test: {
include: ['src/**/*.{test,spec}.{js,ts}']
}
}); I tried adding this part also to the svelte.config.js file: optimizeDeps: {
exclude: ['@node-rs/argon2', '@node-rs/bcrypt']
}, Versions:
The problem is, Oslo requires these packages. I need Lucia Auth, who is including the Oslo package to be functional.. Already threw a lot of hours at it, with all the included frustration. How can I fix this? I realy dont want to go to AWS Amplify or Vercel. Vercel works btw, that is the frustrating part. |
Just got an error error with Svelte 5.0.0-next.133, tried upgrading to Svelte 5.0.0-next.135, also SvelteKit 2.5.8. I've upgraded a lot of packages in the last day and dependabot has been fully broken on pnpm v9 ever since it was released months ago, so I wasn't able to upgrade packages "properly" by running CI for each.
My errors were:
and
Being that neither is a direct dependency of the project, I looked to
oslo
which pulls them in. I had just upgraded tooslo
v1.2.0.Adding this to my
vite.config.ts
fixed it!Not sure if this is an indication of a bug, or if
optimiseDeps
excludingoslo
is just how we configureoslo
now...The text was updated successfully, but these errors were encountered: