-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
Description
Describe the bug
Feels free to point it out if I understand something wrong. #2048 added the support for adapter-node to listen with path. However, because the port still defaults to be 3000 now. The path option would be ignored by node.js.
kit/packages/adapter-node/index.js
Line 65 in 9080b2a
| )}] || '0.0.0.0';\nexport const port = process.env[${JSON.stringify(port_env)}] || 3000;` |
the overload currently using is the options object one:
kit/packages/adapter-node/src/index.js
Line 11 in 9080b2a
| instance.listen(listenOpts, () => { |
As specified in the node.js docs when the port option is specified, the path option would be ignored. Which means it would listen on port 3000 instead of the specified path. Moreover, it would break existing apps using the
PORT environment variable to listening with path. Because in this overload the option.port option would be verified if it's actually a port instead of a path.
The hosting service I am using uses a proxy approach and it uses the PORT variable to pass the named pipe. So honestly, I don't even know the difference between path and port until it breaks. I tried changing the config to let the node adapter to read the PORT variable as a path but it doesn't work.
Reproduction
use a svelte kit app and change the config to this.
// svelte.config.js
import adapt from '@sveltejs/adapter-node';
export default {
kit: {
adapter: adapt({
env: {
path: 'SOME_PATH'
}
})
}
}build the app and run `SOME_PATH=foo node build. Go to localhost:3000 in the browser.
Logs
No response
System Info
System:
OS: Windows 10 10.0.19043
CPU: (16) x64 AMD Ryzen 7 4800HS with Radeon Graphics
Memory: 4.37 GB / 15.42 GB
Binaries:
Node: 16.2.0 - C:\Program Files\nodejs\node.EXE
Yarn: 1.22.10 - ~\AppData\Roaming\npm\yarn.CMD
npm: 7.13.0 - C:\Program Files\nodejs\npm.CMD
Browsers:
Edge: Spartan (44.19041.1023.0), Chromium (92.0.902.73) Internet Explorer: 11.0.19041.906
npmPackages:
@sveltejs/adapter-node: next => 1.0.0-next.42
@sveltejs/kit: next => 1.0.0-next.151
svelte: ^3.34.0 => 3.38.2Severity
blocking an upgrade
Additional Information
No response