Don't force Node to be on the PATH #1676

New Issue

fergalmoran · 2025-08-09T17:21:15Z

fergalmoran commented

2025-08-09 17:21:15 +00:00

Originally created by @andersekdahl on 12/6/2015

From what I can read, the code currently assumes that Node is on the PATH. I think it's a good idea not to bundle a specific version of Node with this package, but it would be great if it was possible to specify where the Node executable is. Would make it easier to deploy multiple sites using this to the same server where the different sites use different Node versions.

*Originally created by @andersekdahl on 12/6/2015* From what I can read, the code currently assumes that Node is on the PATH. I think it's a good idea not to bundle a specific version of Node with this package, but it would be great if it was possible to specify where the Node executable is. Would make it easier to deploy multiple sites using this to the same server where the different sites use different Node versions.

fergalmoran closed this issue

2025-08-09 17:21:15 +00:00

fergalmoran added the P2 core enhancement P2 P2 enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement labels 2025-08-09 17:21:16 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github/JavaScriptServices#1676