Next.js 16 Standalone Build Generates Invalid Chunk Files with Colons for Azure Deployment

[raimonade]

Summary

Next.js 16 standalone build is generating chunk files with colons in their names (like node:inspector), which are invalid for NTFS file systems and cause the GitHub Actions artifact upload to fail.

Additional information

Run actions/upload-artifact@v4
With the provided path, there will be 14116 files uploaded
Artifact name is valid!
Root directory input is valid!
Error: The path for one of the files in artifact is not valid: /apps/dashboard/build/server/chunks/[externals]_node:inspector_7a4283c6._.js. Contains the following character:  Colon :
          
Invalid characters include:  Double quote ", Colon :, Less than <, Greater than >, Vertical bar |, Asterisk *, Question mark ?, Carriage return \r, Line feed \n
          
The following characters are not allowed in files that are uploaded due to limitations with certain file systems such as NTFS. To maintain file system agnostic behavior, these characters are intentionally not allowed to prevent potential problems with downloads on different file systems.

Example

No response

[sonujana26]

this is a known issue with the Next.js 16 standalone + Turbopack build.
Some of the server chunks are generated with names that include colons (like node:inspector), and NTFS / GitHub Actions artifact uploader rejects those characters.

It’s not an Azure problem , it’s the filename convention coming from the new server bundle.

A couple things u can do right now:

1. Disable the “node:” protocol in chunk names (works)

Add this to your next.config.js:

/** @type {import('next').NextConfig} */
const nextConfig = {
  experimental: {
    serverComponentsExternalPackages: [],
  },
  webpack(config) {
    // Rewrite node:foo imports to just foo so the chunk name doesn't contain a colon
    config.resolve.alias = {
      ...config.resolve.alias,
      "node:inspector": "inspector",
    };
    return config;
  },
};

module.exports = nextConfig;

[raimonade]

webpack build flag fixes this for now.