Navigation Menu

Skip to content

Instantly share code, notes, and snippets.

@gera3d
Created July 26, 2018 03:33
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save gera3d/ecbacb8b5357a5d87e80b2e3514ded07 to your computer and use it in GitHub Desktop.
Save gera3d/ecbacb8b5357a5d87e80b2e3514ded07 to your computer and use it in GitHub Desktop.
Command: bash deploy.sh
Handling node.js deployment.
KuduSync.NET from: 'D:\home\site\repository' to: 'D:\home\site\wwwroot'
Copying file: 'scm-commit-id.json'
Using start-up script server.js from package.json.
Node.js versions available on the platform are: 0.6.20, 0.8.2, 0.8.19, 0.8.26, 0.8.27, 0.8.28, 0.10.5, 0.10.18, 0.10.21, 0.10.24, 0.10.26, 0.10.28, 0.10.29, 0.10.31, 0.10.32, 0.10.40, 0.12.0, 0.12.2, 0.12.3, 0.12.6, 4.0.0, 4.1.0, 4.1.2, 4.2.1, 4.2.2, 4.2.3, 4.2.4, 4.3.0, 4.3.2, 4.4.0, 4.4.1, 4.4.6, 4.4.7, 4.5.0, 4.6.0, 4.6.1, 4.8.4, 5.0.0, 5.1.1, 5.3.0, 5.4.0, 5.5.0, 5.6.0, 5.7.0, 5.7.1, 5.8.0, 5.9.1, 6.0.0, 6.1.0, 6.2.2, 6.3.0, 6.5.0, 6.6.0, 6.7.0, 6.9.0, 6.9.1, 6.9.2, 6.9.4, 6.9.5, 6.10.0, 6.10.3, 6.11.1, 6.11.2, 6.11.5, 6.12.2, 6.12.3, 7.0.0, 7.1.0, 7.2.0, 7.3.0, 7.4.0, 7.5.0, 7.6.0, 7.7.0, 7.7.4, 7.10.0, 7.10.1, 8.0.0, 8.1.4, 8.4.0, 8.5.0, 8.7.0, 8.8.0, 8.8.1, 8.9.0, 8.9.3, 8.9.4, 8.10.0, 8.11.1, 10.0.0, 10.6.0.
Selected node.js version 8.9.4. Use package.json file to choose a different version.
Selected npm version 5.3.0
Updating iisnode.yml at D:\home\site\wwwroot\iisnode.yml
npm WARN invalid config scripts-prepend-node-path="--production"
WARN notice [SECURITY] deep-extend has the following vulnerability: 1 low. Go here for more details: https://nodesecurity.io/advisories?search=deep-extend&version=0.4.2 - Run `npm i npm@latest -g` to upgrade your npm version, and then `npm audit` to get more info.
WARN notice [SECURITY] hoek has the following vulnerability: 1 moderate. Go here for more details: https://nodesecurity.io/advisories?search=hoek&version=2.16.3 - Run `npm i npm@latest -g` to upgrade your npm version, and then `npm audit` to get more info.
WARN notice [SECURITY] sshpk has the following vulnerability: 1 high. Go here for more details: https://nodesecurity.io/advisories?search=sshpk&version=1.13.0 - Run `npm i npm@latest -g` to upgrade your npm version, and then `npm audit` to get more info.
WARN notice [SECURITY] tough-cookie has the following vulnerability: 1 high. Go here for more details: https://nodesecurity.io/advisories?search=tough-cookie&version=2.3.2 - Run `npm i npm@latest -g` to upgrade your npm version, and then `npm audit` to get more info.
WARN notice [SECURITY] stringstream has the following vulnerability: 1 moderate. Go here for more details: https://nodesecurity.io/advisories?search=stringstream&version=0.0.5 - Run `npm i npm@latest -g` to upgrade your npm version, and then `npm audit` to get more info.
WARN notice [SECURITY] debug has the following vulnerability: 1 low. Go here for more details: https://nodesecurity.io/advisories?search=debug&version=2.6.8 - Run `npm i npm@latest -g` to upgrade your npm version, and then `npm audit` to get more info.
npm WARN gentlyRm not removing D:\home\site\wwwroot\node_modules\.bin\uuid.cmd as it wasn't installed by D:\home\site\wwwroot\node_modules\node-uuid
npm WARN gentlyRm not removing D:\home\site\wwwroot\node_modules\.bin\uuid as it wasn't installed by D:\home\site\wwwroot\node_modules\node-uuid
npm WARN lifecycle The node binary used for scripts is D:\Program Files (x86)\nodejs\0.10.32\node.exe but npm is using D:\Program Files (x86)\nodejs\8.9.4\node.exe itself. Use the `--scripts-prepend-node-path` option to include the path for the node binary npm was executed with.
> Nightscout@0.10.2-release-20171201 postinstall D:\home\site\wwwroot
> webpack --config webpack.config.js && npm run-script update-buster
D:\home\site\wwwroot\node_modules\webpack\bin\webpack.js:152
yargs.parse(process.argv.slice(2), (err, argv, output) => {
^
SyntaxError: Unexpected token >
at Module._compile (module.js:439:25)
at Object.Module._extensions..js (module.js:474:10)
at Module.load (module.js:356:32)
at Function.Module._load (module.js:312:12)
at Function.Module.runMain (module.js:497:10)
at startup (node.js:119:16)
at node.js:935:3
npm ERR! code ELIFECYCLE
npm ERR! errno 8
npm ERR! Nightscout@0.10.2-release-20171201 postinstall: `webpack --config webpack.config.js && npm run-script update-buster`
npm ERR! Exit status 8
npm ERR!
npm ERR! Failed at the Nightscout@0.10.2-release-20171201 postinstall script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! D:\local\AppData\npm-cache\_logs\2018-07-26T03_20_34_893Z-debug.log
An error has occurred during web site deployment.
npm failed
npm WARN invalid config scripts-prepend-node-path="--production"\r\nWARN notice [SECURITY] deep-extend has the following vulnerability: 1 low. Go here for more details: https://nodesecurity.io/advisories?search=deep-extend&version=0.4.2 - Run `npm i npm@latest -g` to upgrade your npm version, and then `npm audit` to get more info.\r\nWARN notice [SECURITY] hoek has the following vulnerability: 1 moderate. Go here for more details: https://nodesecurity.io/advisories?search=hoek&version=2.16.3 - Run `npm i npm@latest -g` to upgrade your npm version, and then `npm audit` to get more info.\r\nWARN notice [SECURITY] sshpk has the following vulnerability: 1 high. Go here for more details: https://nodesecurity.io/advisories?search=sshpk&version=1.13.0 - Run `npm i npm@latest -g` to upgrade your npm version, and then `npm audit` to get more info.\r\nWARN notice [SECURITY] tough-cookie has the following vulnerability: 1 high. Go here for more details: https://nodesecurity.io/advisories?search=tough-cookie&version=2.3.2 - Run `npm i npm@latest -g` to upgrade your npm version, and then `npm audit` to get more info.\r\nWARN notice [SECURITY] stringstream has the following vulnerability: 1 moderate. Go here for more details: https://nodesecurity.io/advisories?search=stringstream&version=0.0.5 - Run `npm i npm@latest -g` to upgrade your npm version, and then `npm audit` to get more info.\r\nWARN notice [SECURITY] debug has the following vulnerability: 1 low. Go here for more details: https://nodesecurity.io/advisories?search=debug&version=2.6.8 - Run `npm i npm@latest -g` to upgrade your npm version, and then `npm audit` to get more info.\r\nnpm WARN gentlyRm not removing D:\home\site\wwwroot\node_modules\.bin\uuid.cmd as it wasn't installed by D:\home\site\wwwroot\node_modules\node-uuid\r\nnpm WARN gentlyRm not removing D:\home\site\wwwroot\node_modules\.bin\uuid as it wasn't installed by D:\home\site\wwwroot\node_modules\node-uuid\r\nnpm WARN lifecycle The node binary used for scripts is D:\Program Files (x86)\nodejs\0.10.32\node.exe but npm is using D:\Program Files (x86)\nodejs\8.9.4\node.exe itself. Use the `--scripts-prepend-node-path` option to include the path for the node binary npm was executed with.\r\n\r\nD:\home\site\wwwroot\node_modules\webpack\bin\webpack.js:152\r\nyargs.parse(process.argv.slice(2), (err, argv, output) => {\r\n ^\r\nSyntaxError: Unexpected token >\r\n at Module._compile (module.js:439:25)\r\n at Object.Module._extensions..js (module.js:474:10)\r\n at Module.load (module.js:356:32)\r\n at Function.Module._load (module.js:312:12)\r\n at Function.Module.runMain (module.js:497:10)\r\n at startup (node.js:119:16)\r\n at node.js:935:3\r\nnpm ERR! code ELIFECYCLE\r\nnpm ERR! errno 8\r\nnpm ERR! Nightscout@0.10.2-release-20171201 postinstall: `webpack --config webpack.config.js && npm run-script update-buster`\r\nnpm ERR! Exit status 8\r\nnpm ERR! \r\nnpm ERR! Failed at the Nightscout@0.10.2-release-20171201 postinstall script.\r\nnpm ERR! This is probably not a problem with npm. There is likely additional logging output above.\r\n\r\nnpm ERR! A complete log of this run can be found in:\r\nnpm ERR! D:\local\AppData\npm-cache\_logs\2018-07-26T03_20_34_893Z-debug.log\r\nD:\Program Files (x86)\SiteExtensions\Kudu\75.10629.3460\bin\Scripts\starter.cmd bash deploy.sh
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment