Raymond Camden is a Senior Developer Evangelist for Adobe. He works on the Document Services APIs to build powerful (and typically cat-related) PDF demos.
I noticed in the log output that it says it defaulted Node to 0.10.40. Obviously (I'm assuming anyway) you can fix that and specify a Node version, but why would Azure default to such an old version of Node?
Jen Looper is Head of Academic Advocacy at AWS with over 22 years' experience as a web and mobile developer, specializing in creating cross-platform web & mobile apps.
You can definitely fix it by specifying the Node version in your package.json ("engines": {"node": "10.0"},) as the log suggests. But this is the very low default for App Service simply because upgrading is not so easy for big orgs.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I noticed in the log output that it says it defaulted Node to 0.10.40. Obviously (I'm assuming anyway) you can fix that and specify a Node version, but why would Azure default to such an old version of Node?
You can definitely fix it by specifying the Node version in your package.json (
"engines": {"node": "10.0"},) as the log suggests. But this is the very low default for App Service simply because upgrading is not so easy for big orgs.