-
-
Notifications
You must be signed in to change notification settings - Fork 39
Importing server actions using oslo/password
from client components in Next.js causes Webpack errors
#21
Comments
|
|
oslo/password
in Next.js causes Webpack errorsoslo/password
from client components in Next.js causes Webpack errors
oslo/password
from client components in Next.js causes Webpack errorsoslo/password
from client components in Next.js causes Webpack errors
Likely caused by vercel/next.js#60756 |
oslo/password
from client components in Next.js causes Webpack errorsoslo/password
from client components in Next.js causes Webpack errors
Looks like this fixes the issue const nextConfig = {
webpack: (config) => {
config.externals.push("@node-rs/argon2", "@node-rs/bcrypt");
return config;
}
}; |
A similar issue also pops up in jest: error:
` ` const createJestConfig = nextJest({ const clientTestConfig = await createJestConfig({ const serverTestConfig = await createJestConfig({ /** @type {import('jest').Config} / ], export default config; I don't know if there is a way to pass the webpack config to jest |
i have same error |
Same error, and I am using turbopack experimental feature. and it doesn't have an equivalent for the webpack function... |
Using
oslo/password
with theserverComponentsExternalPackages
option in Next.js causes errors when you try to import server actions from"use client"
components. Works fine when for server components. Looks to be the same issue as tursodatabase/libsql-client-ts#128.Using
esmExternals
does not seem to fix the issue, and Oslo doesn't use top-level await.The text was updated successfully, but these errors were encountered: