`next info` unexpectedly interacts with Volta

[chesha1]

Link to the code that reproduces this issue

https://github.com/chesha1/next-reproduce

To Reproduce

use volta install node and pnpm and run command next info

Current vs. Expected behavior

command pnpm next info has the following output:

npm warn Unknown env config "verify-deps-before-run". This will stop working in the next major version of npm.
npm warn Unknown env config "verify-deps-before-run". This will stop working in the next major version of npm.
Volta error: Node is not available.

To run any Node command, first set a default version using `volta install node`
Error details written to /Users/chesha1/.volta/log/volta-error-2026-02-20_22_41_53.209.log
Volta error: Node is not available.

To run any Node command, first set a default version using `volta install node`
Error details written to /Users/chesha1/.volta/log/volta-error-2026-02-20_22_41_53.228.log

Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 25.3.0: Wed Jan 28 20:49:24 PST 2026; root:xnu-12377.81.4~5/RELEASE_ARM64_T8132
  Available memory (MB): 24576
  Available CPU cores: 10
Binaries:
  Node: 24.11.1
  npm: 11.6.2
  Yarn: N/A
  pnpm: 10.29.3
Relevant Packages:
  next: 16.1.6 // Latest available version is detected (16.1.6).
  eslint-config-next: N/A
  react: 19.2.4
  react-dom: 19.2.4
  typescript: 5.9.3
Next.js Config:
  output: N/A

volta-error-2026-02-20_22_41_53.209.log
volta-error-2026-02-20_22_41_53.228.log

Provide environment information

see above

Which area(s) are affected? (Select all that apply)

Not sure

Which stage(s) are affected? (Select all that apply)

next dev (local)

Additional context

No response

[icyJoseph]

Hi, I was about to look at this, but found this:

• https://github.com/volta-cli/volta

Volta is unmaintained. Everything that works today should continue to do so for the foreseeable future, so if it is working for you, there is no particular urgency to migrate to another tool, but we will not be able to address breakages from new OS releases or other changes in the ecosystem, so you should put it on your maintenance roadmap at some point.

I wonder if it is really worth exploring this problem further? If the issue ends up being on Voltas side, we might not be able to fix it at all.

They recommend:

We recommend migrating to mise. See volta-cli/volta#2080.

Is the problem still happening there?

[chesha1]

Hi, thanks for looking into this! I actually didn't realize Volta had become unmaintained — that's news to me. That said, it's still working fine for my day-to-day workflow and I'm honestly too lazy to migrate to a new version manager right now.

Totally understand if this isn't something worth investigating on the Next.js side. Feel free to close this as not planned if you'd like.

[icyJoseph]

I'll close, but, is it only the info command that gave you that error? I'd want to just sanity check that there isn't anything broken in that command.

[chesha1]

Yes, only next info has this issue. next dev and next build work fine.