How do package.json and process.json work? about node HOT 6 CLOSED

@naziml Are there any plans to add support for looking for a start script in the package.json file as well? It would be ideal to have that behavior, to alleviate the need to set the startup file as an App Service setting.

from node.

Your start command can be set to either a PM2 process file (process.json) or just the startup script of your node app (e.g. bin/www). If your startup script is not set at all, we will try to auto-set in this order:

1. Check if bin/www exists and set that if it does
2. Check if server.js exists in site root
3. Check if app.js exists in site root

If your startup script is not set and we don't find any of the above, we will go to a default splash page (hostingstart.js)

HTH,

from node.

👍 to what @lostintangent said. Checking main and scripts.start from package.json would cover most cases.

from node.

Is there any reason this logic isn't included in the image?

I noticed that the Ruby image offloads some things to a startup.sh script. This same kind of thing could be done here to determine the correct start file, exec args (i.e. experimental flags passed to the node bin parsed from env vars), or even to detect the start file.

PACKAGE_PATH=/home/site/wwwroot/package.json # Needs a recursive find instead.
MAIN=$(node -pe "require('$PACKAGE_PATH').main || ''" 2> /dev/null || true)
START=$(node -pe "require('$PACKAGE_PATH').scripts.start || ''" 2> /dev/null || true)

# Fall back to testing for local files.
# ...

There's a lot of potential here. :)

from node.

/cc @Hamster-Huey

from node.

Support for detecting scripts.start and running npm start has been added. Closing this, although it won't be deployed to production for a while.

from node.