npx snowpack build doesn't exit the process on completion

[davidwhitney]

Hey!

It seems like when I try and build a production build with snowpack, it'll the cli functions return but don't process.exit(0) anywhere - effectively hanging my prod builds in CI.

I've reproduced this on both Windows 10, and in WSL2-Ubuntu (in case it's some weirdness with platform support).

Digging through the code, it appears like command$1 on line 4124 in /node_modules/snowpack/dist-node/index.js just returns when watch mode isn't enabled - returning to the cli function, which again just returns and the process continues running.

This seems to come from your TypeScript source here - https://github.com/pikapkg/snowpack/blob/05fcc8c1ad0700ed99638a89077004a27ca45ea2/snowpack/src/index.ts#L107

and

here - https://github.com/pikapkg/snowpack/blob/05fcc8c1ad0700ed99638a89077004a27ca45ea2/snowpack/src/commands/build.ts#L412

I hope I'm not misunderstanding something and looking like a fool, but I've scoured the docs, and I can't see a way to make this work in a CI scenario. I presume the intention is for non-watching non-HMR uses of snowpack to just do their thing and exit?

[FredKSchott]

When Node is done running your program, it should just exit. This is how it works normally, at least.

some plugin may be hanging, do you define any custom plugins that could be causing this?

[davidwhitney]

Apologies for the delay in responding - I've been trying to isolate the behaviour.
I stripped back my configuration to just a single mount setting.

And... well... it gets weirder.

    "mount": {
        "app": "/"
    },

Hangs forever.

    "mount": {
        "/app": "/"
    },

Cleanly exits.

It's exiting cleanly on a GitHub Actions agent, and I'm digging further to try work out what on earth could be causing this in a local repo.
Going through the boring process of removing everything until it works to identify whatever the thing is.

Will keep you posted. Thanks for the response.

[davidwhitney]

Nothing like replying and stumbling towards a solution.

It seems like there was some detritus from some plugins I was originally going to use left in node_modules. After nuking my package lock file, and doing a diff on the broken node_modules, and the working node_modules after a clean NPM install.

There were far more differences than I'd have liked, but the one thing that stood out is that in the broke node_modules folder, there was a copy of @snowpack/plugin-babel. So I followed the hunch that it might be that, dropped it in, tried to reproduce, but no dice. There's definitely something weird, that I can kind of reproduce, but at this point, probably safe to chalk it up to "some weirdness in my modules folder and a broken lockfile" and move on.

Apologies for the narrative, and that I can't quite work out the exact steps to reproduce, but definitely working for me now 🖤