Node Snap Immediately Fails

[Android789515]

Describe the bug

Please provide the following information:

• Description: Running node in any way with concurrently seems to be crashing
• Expected Behavior: Able to run process
• Environment: At least the OS, Node.js, and concurrently's versions

• Concurrently: ^8.2.2
• OS: PopOS Cosmic
• Node: v24.14.1
• pnpm: 10.33.0

• Reproduction: Unsure how reproducible this is.

1. Create scripts

"scripts": {
    "oth": "concurrently \"pnpm start\"",
    "start": "node src/index.js",
  },

2. pnpm oth

───────────────────────────────────────────╮
                                           ╰─────> pnpm oth

> writer-backend@1.0.0 oth /home/untitled1/ProfessionalProjects/writer/backend
> concurrently "pnpm start"

[0]
[0] > writer-backend@1.0.0 start /home/untitled1/ProfessionalProjects/writer/backend
[0] > node src/index.js
[0]
[0]  ELIFECYCLE  Command failed with exit code 1.
[0] pnpm start exited with code 1
 ELIFECYCLE  Command failed with exit code 1.
/home/untitled1/ProfessionalProjects/writer/backend
───────────────────────────────────────────╮
                                           ╰─────> pnpm start

> writer-backend@1.0.0 start /home/untitled1/ProfessionalProjects/writer/backend
> node src/index.js

Writer API listening on port 3001
[EmailService] Initialized with provider: resend
[EmailService] Initialized successfully

Edit

This is also the case with nuxt:

"scripts": {
    "dev": "nuxt dev",
    "build": "nuxt generate",
    "preview": "nuxt preview"
  },

[fe]  ERR_PNPM_RECURSIVE_RUN_FIRST_FAIL  proj@1.0.0 dev: `nuxt dev`
[fe] Exit status 1
[fe]  ELIFECYCLE  Command failed with exit code 1.
[fe] pnpm dev:nuxt exited with code 1

[gustavohenke]

What's in src/index.js?

[Android789515]

What's in src/index.js?

It's an express app.

[Android789515]

I should add that this works on my other operating system.

The OS it works on: Void Linux musl

The OS it isn't working on: PopOS Cosmic

[Android789515]

It looks like any command which uses node in some way will automatically fail:

/home/untitled1/ProfessionalProjects/test
────────────────────────────────────╮
                                    ╰──> pnpm concurrently node
[0] node exited with code 1
/home/untitled1/ProfessionalProjects/test                                                                                                                           1 04/08/2026 05:50:27 AM
────────────────────────────────────╮
                                    ╰──>

/home/untitled1/ProfessionalProjects/test
────────────────────────────────────╮
                                    ╰──> pnpm concurrently npx
[0] npx exited with code 1
/home/untitled1/ProfessionalProjects/test
────────────────────────────────────╮
                                    ╰──> npx

Entering npm script environment at location:
/home/untitled1/ProfessionalProjects/test
Type 'exit' or ^D when finished

$
/home/untitled1/ProfessionalProjects/test                                                                                                                             04/08/2026 05:50:53 AM
────────────────────────────────────╮
                                    ╰──>

/home/untitled1/ProfessionalProjects/test
────────────────────────────────────╮
                                    ╰──> yarn
yarn install v1.22.22
warning package.json: "test" is also the name of a node core module
info No lockfile found.
warning package-lock.json found. Your project contains lock files generated by tools other than Yarn. It is advised not to mix package managers in order to avoid resolution inconsistencies caused by unsynchronized lock files. To clear this warning, remove package-lock.json.
warning test@1.0.0: "test" is also the name of a node core module
[1/4] Resolving packages...
⠁ (node:10629) [DEP0169] DeprecationWarning: `url.parse()` behavior is not standardized and prone to errors that have security implications. Use the WHATWG URL API instead. CVEs are not issued for `url.parse()` vulnerabilities.
(Use `node --trace-deprecation ...` to show where the warning was created)
⠠ string-width@^4.1.0^CError: nu::shell::terminated_by_signal

  × External command was terminated by a signal
   ╭─[repl_entry #21:1:1]
 1 │ yarn
   · ──┬─
   ·   ╰── terminated by SIGINT (2)
   ╰────

/home/untitled1/ProfessionalProjects/test
────────────────────────────────────╮
                                    ╰──> pnpm concurrently yarn
[0] yarn exited with code 1
/home/untitled1/ProfessionalProjects/test                                                                                                                           1 04/08/2026 05:51:10 AM
────────────────────────────────────╮
                                    ╰──>

[gustavohenke]

Thanks. Are you able to do some debugging?
I'm curious about what's happening in your environment - is concurrently perhaps getting a different node than your shell?

[Android789515]

Thanks. Are you able to do some debugging? I'm curious about what's happening in your environment - is concurrently perhaps getting a different node than your shell?

I installed Node through Snap, it seems like that was causing it. Though I'm not sure why, as Snap's binaries were on my $PATH. After reinstalling with a Node version manager everything is working.

It could have been a permissions issue or something, because Snap programs are sandboxed IIRC.

[gustavohenke]

Thanks!

I installed an Ubuntu 24.04 VM, then installed node via Snap, and do get the same exit code 1 when executing through pnpm.
If I execute concurrently directly, node exits with the correct exit code (e.g. node -v => 0, but node -e "throw new Error()" => 1).
Also get no output at all - irrespective of mode.

Seems something funny with how Snap works; there's some interesting information here: nodejs/node#37982 and nodejs/snap#13

Everything seems to work when I use /snap/node/current/bin/node rather than /snap/bin/node though.

I might add a warning to concurrently when it's running through Snap.