After SvelteKit 1.0.0-next.397, build hangs without displaying errors

Describe the bug

After upgrading to any version of SvelteKit after 1.0.0-next.397, when running npm run build (vite build), it gets to a specific point in the process then never completes. No error messages:

% npm run build

> shy-svelte@3.0.3 build
> vite build

vite v3.0.4 building for production...
✓ 1737 modules transformed.

I am using vite@3.0.4 and @sveltejs/adapter-node@1.0.0-next.85. The version of these packages appears to have no effect on the inability to complete the build.

Reproduction

1. git clone https://github.com/nstuyvesant/shy-svelte.git
2. cd shy-svelte
3. Change version of @sveltejs/kit to 1.0.0-next.398 in package.json (or change to “latest”)
4. npm install
5. npx vite build (or npm run build) - use first one if you don’t want to include my post-build script (will reproduce issue easily)

This build will never complete (or throw an error).

Change the SvelteKit version back to 1.0.0-next.397 and retry. Build will complete without problems.

Logs

% npm run build

> shy-svelte@3.0.3 build
> vite build

vite v3.0.4 building for production...
✓ 1737 modules transformed.

System Info

System:
    OS: macOS 12.4
    CPU: (10) arm64 Apple M1 Pro
    Memory: 1.90 GB / 32.00 GB
    Shell: 5.8.1 - /bin/zsh
  Binaries:
    Node: 18.7.0 - /opt/homebrew/bin/node
    npm: 8.15.1 - /opt/homebrew/bin/npm
  Browsers:
    Chrome: 103.0.5060.134
    Firefox: 102.0.1
    Safari: 15.5
  npmPackages:
    @sveltejs/adapter-node: latest => 1.0.0-next.85 
    @sveltejs/kit: 1.0.0-next.397 => 1.0.0-next.397 
    svelte: ^3.49.0 => 3.49.0 
    vite: ^3.0.4 => 3.0.4

Severity

blocking an upgrade

Additional Information

Another person on Discord ran into this with their project as well. A change in 1.0.0-next.398 in combination with my project seems to be the cause.

[nstuyvesant]

Thanks! My build just completed with 1.0.0-next.402

[jiyosub]

On discord, saw some comments about builds getting very long (went from 30 seconds to 15 minutes) after 1.0.0-next.397. Perhaps related?

That was mine.