Replies: 3 comments 2 replies
-
|
We have the same issue where we can't deploy our current pipeline using It seems that the documentation is mentioned that it will be supported in Appreciate how to resolve this issue and what is the workaround. |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
I found out that the check for |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
I can't fully reproduce this 🤔 does anyone have a repository? I am seeing some warnings when dev uses turbopack, but anything other than that, things seem to work? Tested with |
Beta Was this translation helpful? Give feedback.
2 replies
-
|
I have the same issue. I cannot share my repo, but I can share logs if that helps. I am on Output of My // @ts-nocheck
/* eslint-disable */
/**
* Run `build` or `dev` with `SKIP_ENV_VALIDATION` to skip env validation. This is especially useful
* for Docker builds.
*/
import { NextConfig } from "next";
import NextPWA from "next-pwa";
import { env } from "./src/env";
import { NextJsWebpackConfig } from "next/dist/server/config-shared";
const isProd = env.NODE_ENV === "production";
const webpack: NextJsWebpackConfig = (
config: NextConfig,
{ isServer }: { isServer: boolean },
) => {
// Only apply webpack config when not using Turbopack
if (!isServer) {
config.resolve.fallback = { ...config.resolve.fallback, fs: false };
}
config.resolve.alias = {
...config.resolve.alias,
vertx: "src/vertx-stub",
};
config.module.rules.push({
test: /\.sql$/,
type: "asset/source",
});
config.ignoreWarnings = [
{
module: /@opentelemetry\/instrumentation/,
message: /Critical dependency/,
},
{
module: /@prisma\/instrumentation/,
message: /Critical dependency/,
},
{
message: /Critical dependency/,
},
// Add Edge Runtime warning ignores
{
message: /not supported in the Edge Runtime/,
},
{
message: /module.*is loaded.*which is not supported/,
},
];
return config;
};
const config: NextConfig = {
// Turbopack configuration
turbopack: {},
// Webpack config for building
...(process.env.NODE_ENV !== "development" || !process.env.TURBOPACK
? { webpack }
: {}),
modularizeImports: {
"@tabler/icons-react": {
transform: "@tabler/icons-react/dist/esm/icons/{{member}}",
},
},
images: {
remotePatterns: [
{
protocol: "https",
hostname: "**",
port: "",
pathname: "**",
},
],
},
compress: isProd,
transpilePackages: [
"@tanstack/react-query",
"@tanstack/query-core",
"@t3-oss/env-core",
"@t3-oss/env-nextjs",
"@vercel/otel",
"@azure/core-rest-pipeline",
"@azure/logger",
"@azure/core-util",
"@azure/abort-controller",
"@azure/core-tracing",
"@azure/core-client",
"@opentelemetry/instrumentation-winston",
"next-auth",
],
};
export default config;My middleware is in I am on Windows |
Beta Was this translation helpful? Give feedback.
-
|
Hi, but you are using |
Beta Was this translation helpful? Give feedback.
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.
Uh oh!
There was an error while loading. Please reload this page.
-
Summary
I'm excited that the node middleware support is stabilizing (https://github.com/vercel/next.js/releases/tag/v15.4.2-canary.13). Kudos to everyone involved 🙏 🙇
When switching to 15.4.2-canary.15 and removing the:
from next.config, and starting the app I get "Cannot find middleware module".
The file structure of the next.js project:
The project is also using
"next-intl": "^3.26.5"if that matters somehow :DHelp 🙏 What am I doing wrong?
Additional information
Beta Was this translation helpful? Give feedback.
All reactions