I'm trying to generate a static website with nuxt and vuetify.
And when I type npm run generate/build im getting this error too but I don't know if its the reason.
ERROR Missing or incomplete config for current environment 'development': key 'databaseURL' is required!
0 info it worked if it ends with ok
1 verbose cli [
1 verbose cli 'd:\\Program Files\\nodejs\\node.exe',
1 verbose cli 'd:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js',
1 verbose cli 'run',
1 verbose cli 'generate'
1 verbose cli ]
2 info using npm#6.10.2
3 info using node#v12.8.1
4 verbose run-script [ 'pregenerate', 'generate', 'postgenerate' ]
5 info lifecycle mywebsite#1.0.0~pregenerate: mywebsite#1.0.0
6 info lifecycle mywebsite#1.0.0~generate: mywebsite#1.0.0
7 verbose lifecycle mywebsite#1.0.0~generate: unsafe-perm in lifecycle true
8 verbose lifecycle mywebsite#1.0.0~generate: PATH: d:\Program Files\nodejs\node_modules\npm\node_modules\npm-lifecycle\node-gyp-bin;F:\PROYECTOS\VUEJS\NUXT PROJECTS\mywebsite\node_modules\.bin;c:\program files (x86)\common files\oracle\java\javapath;c:\windows\system32;c:\windows;c:\windows\system32\wbem;c:\windows\system32\windowspowershell\v1.0\;c:\program files (x86)\intel\intel(r) management engine components\dal;c:\program files\intel\intel(r) management engine components\dal;c:\windows\system32\openssh\;c:\program files\nvidia corporation\nvidia nvdlisr;c:\users\maattz\appdata\roaming\python\python37\scripts;d:\program files\nodejs\;d:\cygwin64\bin;d:\program files\dotnet\;d:\program files\microsoft sql server\130\tools\binn\;d:\program files\microsoft sql server\client sdk\odbc\170\tools\binn\;d:\program files\git\cmd;d:\xampp\php;c:\msys64\mingw64\bin;D:\Program Files\NVIDIA Corporation\NVIDIA NvDLISR;;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\WINDOWS\System32\OpenSSH\;D:\Python\Scripts\;D:\Python\;C:\Users\MAATTZ\AppData\Local\Microsoft\WindowsApps;C:\Users\MAATTZ\AppData\Local\atom\bin;D:\Program Files (x86)\Microsoft VS Code\bin;C:\Users\MAATTZ\AppData\Roaming\npm;C:\Users\MAATTZ\AppData\Local\Microsoft\WindowsApps;C:\Users\MAATTZ\AppData\Local\GitHubDesktop\bin;C:\Users\MAATTZ\Documents\mis apps;D:\ffmpeg
9 verbose lifecycle mywebsite#1.0.0~generate: CWD: F:\PROYECTOS\VUEJS\NUXT PROJECTS\mywebsite
10 silly lifecycle mywebsite#1.0.0~generate: Args: [ '/d /s /c', 'nuxt generate' ]
11 silly lifecycle mywebsite#1.0.0~generate: Returned: code: 1 signal: null
12 info lifecycle mywebsite#1.0.0~generate: Failed to exec generate script
13 verbose stack Error: mywebsite#1.0.0 generate: `nuxt generate`
13 verbose stack Exit status 1
13 verbose stack at EventEmitter.<anonymous> (d:\Program Files\nodejs\node_modules\npm\node_modules\npm-lifecycle\index.js:326:16)
13 verbose stack at EventEmitter.emit (events.js:203:13)
13 verbose stack at ChildProcess.<anonymous> (d:\Program Files\nodejs\node_modules\npm\node_modules\npm-lifecycle\lib\spawn.js:55:14)
13 verbose stack at ChildProcess.emit (events.js:203:13)
13 verbose stack at maybeClose (internal/child_process.js:1021:16)
13 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:283:5)
14 verbose pkgid mywebsite#1.0.0
15 verbose cwd F:\PROYECTOS\VUEJS\NUXT PROJECTS\mywebsite
16 verbose Windows_NT 10.0.19042
17 verbose argv "d:\\Program Files\\nodejs\\node.exe" "d:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "run" "generate"
18 verbose node v12.8.1
19 verbose npm v6.10.2
20 error code ELIFECYCLE
21 error errno 1
22 error mywebsite#1.0.0 generate: `nuxt generate`
22 error Exit status 1
23 error Failed at the mywebsite#1.0.0 generate script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 1, true ]
Related
I am trying to learn the basics of .NET Core and I have installed the .NET SDK 2.2 for Linux (I am using Windows Subsystem for Linux). I want to build a Web App with the Angular framework, so I got this GitHub repository on my machine with these two commands:
$ dotnet tool install -g web
$ web new angular-spa ProjectName
Now, basically the next step would be a simple
npm run dev
but when I try this in bash, I get some errors:
0 info it worked if it ends with ok
1 verbose cli [ '/usr/bin/node', '/usr/bin/npm', 'run', 'dev' ]
2 info using npm#3.5.2
3 info using node#v8.10.0
4 verbose run-script [ 'predev', 'dev', 'postdev' ]
5 info lifecycle my-app#0.0.0~predev: my-app#0.0.0
6 silly lifecycle my-app#0.0.0~predev: no script for predev, continuing
7 info lifecycle my-app#0.0.0~dev: my-app#0.0.0
8 verbose lifecycle my-app#0.0.0~dev: unsafe-perm in lifecycle true
9 verbose lifecycle my-app#0.0.0~dev: PATH: /usr/share/npm/bin/node-gyp-bin:/mnt/c/Users/rober/OneDrive/Dev Place/Developer Place/C#/dotnetWSL/angularAPP/AngularApp/MyApp/node_modules/.bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/mnt/c/Windows/System32:/mnt/c/Windows:/mnt/c/Windows/System32/wbem:/mnt/c/Windows/System32/WindowsPowerShell/v1.0:/mnt/c/Windows/System32/OpenSSH:/mnt/c/Program Files/Microsoft VS Code/bin:/mnt/c/Program Files (x86)/Wolfram Research/WolframScript:/mnt/c/Users/rober/AppData/Local/Microsoft/WindowsApps:/mnt/c/Users/rober/AppData/Local/hyper/app-3.0.2/resources/bin:/mnt/c/Users/rober/AppData/Local/GitHubDesktop/bin:/snap/bin:/home/basavyr/.dotnet/tools
10 verbose lifecycle my-app#0.0.0~dev: CWD: /mnt/c/Users/rober/OneDrive/Dev Place/Developer Place/C#/dotnetWSL/angularAPP/AngularApp/MyApp
11 silly lifecycle my-app#0.0.0~dev: Args: [ '-c', 'ng build --aot --watch' ]
12 silly lifecycle my-app#0.0.0~dev: Returned: code: 1 signal: null
13 info lifecycle my-app#0.0.0~dev: Failed to exec dev script
14 verbose stack Error: my-app#0.0.0 dev: `ng build --aot --watch`
14 verbose stack Exit status 1
14 verbose stack at EventEmitter.<anonymous> (/usr/share/npm/lib/utils/lifecycle.js:232:16)
14 verbose stack at emitTwo (events.js:126:13)
14 verbose stack at EventEmitter.emit (events.js:214:7)
14 verbose stack at ChildProcess.<anonymous> (/usr/share/npm/lib/utils/spawn.js:24:14)
14 verbose stack at emitTwo (events.js:126:13)
14 verbose stack at ChildProcess.emit (events.js:214:7)
14 verbose stack at maybeClose (internal/child_process.js:925:16)
14 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:209:5)
15 verbose pkgid my-app#0.0.0
16 verbose cwd /mnt/c/Users/rober/OneDrive/Dev Place/Developer Place/C#/dotnetWSL/angularAPP/AngularApp/MyApp
17 error Linux 4.4.0-17763-Microsoft
18 error argv "/usr/bin/node" "/usr/bin/npm" "run" "dev"
19 error node v8.10.0
20 error npm v3.5.2
21 error code ELIFECYCLE
22 error my-app#0.0.0 dev: `ng build --aot --watch`
22 error Exit status 1
23 error Failed at the my-app#0.0.0 dev script 'ng build --aot --watch'.
23 error Make sure you have the latest version of node.js and npm installed.
23 error If you do, this is most likely a problem with the my-app package,
23 error not with npm itself.
23 error Tell the author that this fails on your system:
23 error ng build --aot --watch
23 error You can get information on how to open an issue for this project with:
23 error npm bugs my-app
23 error Or if that isn't available, you can get their info via:
23 error npm owner ls my-app
23 error There is likely additional logging output above.
24 verbose exit [ 1, true ]
From what I see here, the npm or node versions are not the latest ones, however, I did an update today just to make sure and the issue is still here.
I would appreciate any help. Please remember that I am new to the concept of .NET web apps and my experience with Angular is also minimal: I recently started to get familiarized.
When i start a react using npm run wpstart for Wordpress Theme is starts for the first time perfectly, but for the second time when i start it again to run a theme it throws all the time this kind of error. I have given a full permission to my project folder.
0 info it worked if it ends with ok
1 verbose cli [ '/usr/bin/node', '/usr/bin/npm', 'run', 'start' ]
2 info using npm#6.4.1
3 info using node#v8.15.0
4 verbose run-script [ 'prestart', 'start', 'poststart' ]
5 info lifecycle wpproject#0.1.0~prestart: wpproject#0.1.0
6 info lifecycle wpproject#0.1.0~start: wpproject#0.1.0
7 verbose lifecycle wpproject#0.1.0~start: unsafe-perm in lifecycle true
8 verbose lifecycle wpproject#0.1.0~start: PATH: /usr/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/var/www/html/projectname/wp-content/themes/wpproject/react-src/node_modules/.bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin:/usr/lib/jvm/java-8-oracle/bin:/usr/lib/jvm/java-8-oracle/db/bin:/usr/lib/jvm/java-8-oracle/jre/bin
9 verbose lifecycle wpproject#0.1.0~start: CWD: /var/www/html/projectname/wp-content/themes/wpproject/react-src
10 silly lifecycle wpproject#0.1.0~start: Args: [ '-c', 'wptheme-scripts start' ]
11 silly lifecycle wpproject#0.1.0~start: Returned: code: 1 signal: null
12 info lifecycle wpproject#0.1.0~start: Failed to exec start script
13 verbose stack Error: wpproject#0.1.0 start: `wptheme-scripts start`
13 verbose stack Exit status 1
13 verbose stack at EventEmitter.<anonymous> (/usr/lib/node_modules/npm/node_modules/npm-lifecycle/index.js:301:16)
13 verbose stack at emitTwo (events.js:126:13)
13 verbose stack at EventEmitter.emit (events.js:214:7)
13 verbose stack at ChildProcess.<anonymous> (/usr/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14)
13 verbose stack at emitTwo (events.js:126:13)
13 verbose stack at ChildProcess.emit (events.js:214:7)
13 verbose stack at maybeClose (internal/child_process.js:915:16)
13 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:209:5)
14 verbose pkgid wpproject#0.1.0
15 verbose cwd /var/www/html/projectname/wp-content/themes/wpproject/react-src
16 verbose Linux 4.15.0-45-generic
17 verbose argv "/usr/bin/node" "/usr/bin/npm" "run" "start"
18 verbose node v8.15.0
19 verbose npm v6.4.1
20 error code ELIFECYCLE
21 error errno 1
22 error wpproject#0.1.0 start: `wptheme-scripts start`
22 error Exit status 1
23 error Failed at the wpproject#0.1.0 start script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 1, true ]
The error EADDRINUSE :::8090 means the port in which you are trying to run the project is in use, to avoid this error you can kill the process running on the port and run the project.
I'm running OsX 10.9.5 and React 16. After meteor installation fallowed by instruction from site https://www.meteor.com/install, installation process goes without any problems.
When I'm trying run meteor from terminal meteor run I get this:
[[[[[ ~/Codding/cdbioffice ]]]]]
=> Started proxy.
dyld: Symbol not found: _fchmodat
Referenced from:
/Users/lukasz/.meteor/packages/meteor-tool/.1.8.0_2.cty1uc.prsil++os.osx.x86_64+web.browser+web.browser.legacy+web.cordova/mt-os.osx.x86_64/dev_bundle/mongodb/bin/mongod
Expected in: /usr/lib/libSystem.B.dylib
in
/Users/lukasz/.meteor/packages/meteor-tool/.1.8.0_2.cty1uc.prsil++os.osx.x86_64+web.browser+web.browser.legacy+web.cordova/mt-os.osx.x86_64/dev_bundle/mongodb/bin/mongod
Unexpected mongo exit code null. Restarting.
dyld: Symbol not found: _fchmodat
Referenced from:
/Users/lukasz/.meteor/packages/meteor-tool/.1.8.0_2.cty1uc.prsil++os.osx.x86_64+web.browser+web.browser.legacy+web.cordova/mt-os.osx.x86_64/dev_bundle/mongodb/bin/mongod
Expected in: /usr/lib/libSystem.B.dylib
in
/Users/lukasz/.meteor/packages/meteor-tool/.1.8.0_2.cty1uc.prsil++os.osx.x86_64+web.browser+web.browser.legacy+web.cordova/mt-os.osx.x86_64/dev_bundle/mongodb/bin/mongod
Unexpected mongo exit code null. Restarting.
dyld: Symbol not found: _fchmodat
Referenced from:
/Users/lukasz/.meteor/packages/meteor-tool/.1.8.0_2.cty1uc.prsil++os.osx.x86_64+web.browser+web.browser.legacy+web.cordova/mt-os.osx.x86_64/dev_bundle/mongodb/bin/mongod
Expected in: /usr/lib/libSystem.B.dylib
in
/Users/lukasz/.meteor/packages/meteor-tool/.1.8.0_2.cty1uc.prsil++os.osx.x86_64+web.browser+web.browser.legacy+web.cordova/mt-os.osx.x86_64/dev_bundle/mongodb/bin/mongod
Unexpected mongo exit code null. Restarting.
Can't start Mongo server
In VisualStudio from project directory after meteor npm start in terminal I get additional info:
npm ERR! code ELIFECYCLE
npm ERR! errno 254
npm ERR! cd-bioffice-meteor# start: `meteor run --settings settings.json`
npm ERR! Exit status 254
npm ERR!
npm ERR! Failed at the cd-bioffice-meteor# start 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! /Users/lukasz/.npm/_logs/2019-01-14T13_48_22_707Z-debug.log
and in log file:
0 info it worked if it ends with ok
1 verbose cli [ '/Users/lukasz/.meteor/packages/meteor-tool/.1.8.0_2.cty1uc.prsil++os.osx.x86_64+web.browser+web.browser.legacy+web.cordova/mt-os.osx.x86_64/dev_bundle/bin/node',
1 verbose cli '/Users/lukasz/.meteor/packages/meteor-tool/.1.8.0_2.cty1uc.prsil++os.osx.x86_64+web.browser+web.browser.legacy+web.cordova/mt-os.osx.x86_64/dev_bundle/bin/npm',
1 verbose cli 'start' ]
2 info using npm#6.4.1
3 info using node#v8.11.4
4 verbose run-script [ 'prestart', 'start', 'poststart' ]
5 info lifecycle cd-bioffice-meteor#~prestart: cd-bioffice-meteor#
6 info lifecycle cd-bioffice-meteor#~start: cd-bioffice-meteor#
7 verbose lifecycle cd-bioffice-meteor#~start: unsafe-perm in lifecycle true
8 verbose lifecycle cd-bioffice-meteor#~start: PATH: /Users/lukasz/.meteor/packages/meteor-tool/.1.8.0_2.cty1uc.prsil++os.osx.x86_64+web.browser+web.browser.legacy+web.cordova/mt-os.osx.x86_64/dev_bundle/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/Users/lukasz/Codding/cdbioffice/node_modules/.bin:/Users/lukasz/.meteor/packages/meteor-tool/.1.8.0_2.cty1uc.prsil++os.osx.x86_64+web.browser+web.browser.legacy+web.cordova/mt-os.osx.x86_64/dev_bundle/bin:/Users/lukasz/.meteor/packages/meteor-tool/.1.8.0_2.cty1uc.prsil++os.osx.x86_64+web.browser+web.browser.legacy+web.cordova/mt-os.osx.x86_64:/Users/lukasz/.meteor/packages/meteor-tool/.1.8.0_2.cty1uc.prsil++os.osx.x86_64+web.browser+web.browser.legacy+web.cordova/mt-os.osx.x86_64/dev_bundle/lib/node_modules/.bin:/Users/lukasz/.npm-global/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/opt/X11/bin:/usr/local/MacGPG2/bin:/Users/lukasz/.npm-global/bin
9 verbose lifecycle cd-bioffice-meteor#~start: CWD: /Users/lukasz/Codding/cdbioffice
10 silly lifecycle cd-bioffice-meteor#~start: Args: [ '-c', 'meteor run --settings settings.json' ]
11 silly lifecycle cd-bioffice-meteor#~start: Returned: code: 254 signal: null
12 info lifecycle cd-bioffice-meteor#~start: Failed to exec start script
13 verbose stack Error: cd-bioffice-meteor# start: `meteor run --settings settings.json`
13 verbose stack Exit status 254
13 verbose stack at EventEmitter.<anonymous> (/Users/lukasz/.meteor/packages/meteor-tool/.1.8.0_2.cty1uc.prsil++os.osx.x86_64+web.browser+web.browser.legacy+web.cordova/mt-os.osx.x86_64/dev_bundle/lib/node_modules/npm/node_modules/npm-lifecycle/index.js:301:16)
13 verbose stack at emitTwo (events.js:126:13)
13 verbose stack at EventEmitter.emit (events.js:214:7)
13 verbose stack at ChildProcess.<anonymous> (/Users/lukasz/.meteor/packages/meteor-tool/.1.8.0_2.cty1uc.prsil++os.osx.x86_64+web.browser+web.browser.legacy+web.cordova/mt-os.osx.x86_64/dev_bundle/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14)
13 verbose stack at emitTwo (events.js:126:13)
13 verbose stack at ChildProcess.emit (events.js:214:7)
13 verbose stack at maybeClose (internal/child_process.js:925:16)
13 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:209:5)
14 verbose pkgid cd-bioffice-meteor#
15 verbose cwd /Users/lukasz/Codding/cdbioffice
16 verbose Darwin 13.4.0
17 verbose argv "/Users/lukasz/.meteor/packages/meteor-tool/.1.8.0_2.cty1uc.prsil++os.osx.x86_64+web.browser+web.browser.legacy+web.cordova/mt-os.osx.x86_64/dev_bundle/bin/node" "/Users/lukasz/.meteor/packages/meteor-tool/.1.8.0_2.cty1uc.prsil++os.osx.x86_64+web.browser+web.browser.legacy+web.cordova/mt-os.osx.x86_64/dev_bundle/bin/npm" "start"
18 verbose node v8.11.4
19 verbose npm v6.4.1
20 error code ELIFECYCLE
21 error errno 254
22 error cd-bioffice-meteor# start: `meteor run --settings settings.json`
22 error Exit status 254
23 error Failed at the cd-bioffice-meteor# start script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 254, true ]
What I'm doing wrong? I found bunch of answer on this topic but I'm not sure witch direction should I go. One of them is that OsX 10.9 is to old to run that config. I don't want to make this situation worst.
System:
Maverics 10.9.5
node -v && npm -v
v9.5.0
5.6.0
Thanks for your help.
package.json for existing project (I'm interested on):
{
"name": "cd-bioffice-meteor",
"private": true,
"scripts": {
"start": "meteor run --settings settings.json",
"test": "meteor test --once --driver-package meteortesting:mocha",
"test-app": "TEST_WATCH=1 meteor test --full-app --driver-package meteortesting:mocha",
"visualize": "meteor --production --extra-packages bundle-visualizer"
},
"dependencies": {
"#babel/runtime": "^7.1.5",
"bcrypt": "^3.0.0",
"meteor-node-stubs": "^0.4.1",
"moment": "^2.22.2",
"moment-timezone": "^0.5.21",
"npm": "^6.5.0",
"polished": "^2.0.3",
"react": "^16.5.1",
"react-bootstrap": "^0.32.4",
"react-dom": "^16.5.1",
"react-inlinesvg": "^0.8.1",
"react-router-bootstrap": "^0.24.4",
"react-router-dom": "^4.3.1",
"serialport": "^7.1.3",
"styled-components": "^3.4.6"
},
"meteor": {
"mainModule": {
"client": "client/main.jsx",
"server": "server/main.js"
},
"testModule": "tests/main.js"
}
}
Visual studio will not allow me to publish my ASP.NET core 2 project anymore, creating the following output
12/21/2018 1:44:52 PM System.AggregateException: One or more errors
occurred. ---> System.Exception: Build failed. Check the Output window
for more details. --- End of inner exception stack trace --- at
System.Threading.Tasks.Task.ThrowIfExceptional(Boolean
includeTaskCanceledExceptions) at
System.Threading.Tasks.Task.Wait(Int32 millisecondsTimeout,
CancellationToken cancellationToken) at
Microsoft.VisualStudio.Web.Publish.PublishService.VsWebProjectPublish.<>c__DisplayClass43_0.b__2()
at System.Threading.Tasks.Task`1.InnerInvoke() at
System.Threading.Tasks.Task.Execute()
--- End of stack trace from previous location where exception was thrown --- at
System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task
task) at
System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task
task) at
Microsoft.VisualStudio.ApplicationCapabilities.Publish.ViewModel.ProfileSelectorViewModel.d__127.MoveNext()
---> (Inner Exception #0) System.Exception: Build failed. Check the Output window for more details.<---
===================
I've checked other threads regarding NPM exit with code 1 but neither one seems relevant to me.
I was able to publish project once and the second time I've tried - Got the error. No configuration was changed.
EDIT
Npm Error Log:
0 info it worked if it ends with ok
1 verbose cli [ 'C:\\Program Files\\nodejs\\node.exe',
1 verbose cli 'C:\\Users\\asmirnov\\AppData\\Roaming\\npm\\node_modules\\npm\\bin\\npm-cli.js',
1 verbose cli 'run',
1 verbose cli 'build' ]
2 info using npm#6.4.1
3 info using node#v8.11.4
4 verbose run-script [ 'prebuild', 'build', 'postbuild' ]
5 info lifecycle v7#0.1.0~prebuild: v7#0.1.0
6 info lifecycle v7#0.1.0~build: v7#0.1.0
7 verbose lifecycle v7#0.1.0~build: unsafe-perm in lifecycle true
8 verbose lifecycle v7#0.1.0~build: PATH: C:\Users\asmirnov\AppData\Roaming\npm\node_modules\npm\node_modules\npm-lifecycle\node-gyp-bin;C:\dev\DigiSign\DigiSign2018_UAT\SimplySignWeb\v7\ClientApp\node_modules\.bin;C:\Program Files (x86)\Common Files\Oracle\Java\javapath;C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\iCLS\;C:\Program Files\Intel\Intel(R) Management Engine Components\iCLS\;C:\ProgramData\Oracle\Java\javapath;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\Intel\UCRT\;C:\Program Files\Intel\UCRT\;C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\DAL;C:\Program Files\Intel\Intel(R) Management Engine Components\DAL;C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\IPT;C:\Program Files\Intel\Intel(R) Management Engine Components\IPT;C:\Windows\system32\config\systemprofile\.dnx\bin;C:\Program Files\Microsoft DNX\Dnvm\;C:\Program Files (x86)\Microsoft SQL Server\Client SDK\ODBC\130\Tools\Binn\;C:\Program Files (x86)\Microsoft SQL Server\130\Tools\Binn\;C:\Program Files (x86)\Microsoft SQL Server\130\DTS\Binn\;C:\Program Files (x86)\Microsoft SQL Server\130\Tools\Binn\ManagementStudio\;C:\Program Files\dotnet\;C:\Program Files\Microsoft SQL Server\130\Tools\Binn\;C:\Program Files\PuTTY\;C:\Program Files (x86)\AMD\ATI.ACE\Core-Static;C:\Program Files\nodejs\;C:\Program Files\Git\cmd;C:\Program Files (x86)\Toshiba\Bluetooth Toshiba Stack\sys\;C:\Program Files (x86)\Toshiba\Bluetooth Toshiba Stack\sys\x64\;C:\Program Files (x86)\Rico Suter\NSwagStudio\;C:\Users\asmirnov\.dotnet\tools;C:\Users\asmirnov\AppData\Roaming\npm;C:\ProgramData\asmirnov\atom\bin;C:\Users\asmirnov\AppData\Local\Programs\Microsoft VS Code\bin;C:\Users\asmirnov\AppData\Local\Programs\Fiddler
9 verbose lifecycle v7#0.1.0~build: CWD: C:\dev\DigiSign\DigiSign2018_UAT\SimplySignWeb\v7\ClientApp
10 silly lifecycle v7#0.1.0~build: Args: [ '/d /s /c', 'node scripts/build.js' ]
11 silly lifecycle v7#0.1.0~build: Returned: code: 1 signal: null
12 info lifecycle v7#0.1.0~build: Failed to exec build script
13 verbose stack Error: v7#0.1.0 build: `node scripts/build.js`
13 verbose stack Exit status 1
13 verbose stack at EventEmitter.<anonymous> (C:\Users\asmirnov\AppData\Roaming\npm\node_modules\npm\node_modules\npm-lifecycle\index.js:301:16)
13 verbose stack at emitTwo (events.js:126:13)
13 verbose stack at EventEmitter.emit (events.js:214:7)
13 verbose stack at ChildProcess.<anonymous> (C:\Users\asmirnov\AppData\Roaming\npm\node_modules\npm\node_modules\npm-lifecycle\lib\spawn.js:55:14)
13 verbose stack at emitTwo (events.js:126:13)
13 verbose stack at ChildProcess.emit (events.js:214:7)
13 verbose stack at maybeClose (internal/child_process.js:925:16)
13 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:209:5)
14 verbose pkgid v7#0.1.0
15 verbose cwd C:\dev\DigiSign\DigiSign2018_UAT\SimplySignWeb\v7\ClientApp
16 verbose Windows_NT 6.1.7601
17 verbose argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Users\\asmirnov\\AppData\\Roaming\\npm\\node_modules\\npm\\bin\\npm-cli.js" "run" "build"
18 verbose node v8.11.4
19 verbose npm v6.4.1
20 error code ELIFECYCLE
21 error errno 1
22 error v7#0.1.0 build: `node scripts/build.js`
22 error Exit status 1
23 error Failed at the v7#0.1.0 build script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 1, true ]
I was able to figure out what the problem is by rinning build in a console, it pointed me to the problem in one of the components that wasn't compiling:
In my case I had a dash " - " in the file path, in one of the folder names. Renamed the folder and it worked.
I run into error when I tried to host Google Analytics's demo site locally.(https://github.com/googleanalytics/ga-dev-tools)
Please help. Thanks a lot.
I have absolutely no programming / dev background (1st time using Github) and after many hours of struggling I finally made it to this last step, yet still not able to host the site myself.
Tried to update npm and node.js version to the latest but still not working. The first lines of error seeing on command prompt is:
Starting 'serve'...
'serve' errored after 6.62ms
Error: spawn UNKNOWN
Looking for a solution. The log is below:
0 info it worked if it ends with ok
1 verbose cli [ 'C:\Program Files\nodejs\node.exe',
1 verbose cli 'C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js',
1 verbose cli 'start' ]
2 info using npm#4.2.0
3 info using node#v7.8.0
4 verbose run-script [ 'prestart', 'start', 'poststart' ]
5 info lifecycle ga-dev-tools#~prestart: ga-dev-tools#
6 silly lifecycle ga-dev-tools#~prestart: no script for prestart, continuing
7 info lifecycle ga-dev-tools#~start: ga-dev-tools#
8 verbose lifecycle ga-dev-tools#~start: unsafe-perm in lifecycle true
9 verbose lifecycle ga-dev-tools#~start: PATH: C:\Program Files\nodejs\node_modules\npm\bin\node-gyp-bin;c:\GitHub\ga-dev-tools\node_modules.bin;c:\program files\graphicsmagick-1.3.25-q16;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0;C:\Program Files\Google\Cloud SDK\google-cloud-sdk.install.backup\platform\bundledpython\Scripts;C:\Program Files\GraphicsMagick-1.3.25-Q16;C:\Program Files\Google\Cloud SDK\google-cloud-sdk\bin;C:\Users\Administrator\AppData\Local\GitHub;C:\Program Files\Git\cmd;C:\Program Files\Git;C:\Program Files\nodejs;;C:\Program Files\Google\Cloud SDK\google-cloud-sdk\bin;C:\Users\Administrator\AppData\Roaming\npm
10 verbose lifecycle ga-dev-tools#~start: CWD: c:\GitHub\ga-dev-tools
11 silly lifecycle ga-dev-tools#~start: Args: [ '/d /s /c', 'gulp watch' ]
12 silly lifecycle ga-dev-tools#~start: Returned: code: 1 signal: null
13 info lifecycle ga-dev-tools#~start: Failed to exec start script
14 verbose stack Error: ga-dev-tools# start: gulp watch
14 verbose stack Exit status 1
14 verbose stack at EventEmitter. (C:\Program Files\nodejs\node_modules\npm\lib\utils\lifecycle.js:279:16)
14 verbose stack at emitTwo (events.js:106:13)
14 verbose stack at EventEmitter.emit (events.js:194:7)
14 verbose stack at ChildProcess. (C:\Program Files\nodejs\node_modules\npm\lib\utils\spawn.js:40:14)
14 verbose stack at emitTwo (events.js:106:13)
14 verbose stack at ChildProcess.emit (events.js:194:7)
14 verbose stack at maybeClose (internal/child_process.js:899:16)
14 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:226:5)
15 verbose pkgid ga-dev-tools#
16 verbose cwd c:\GitHub\ga-dev-tools
17 error Windows_NT 6.1.7601
18 error argv "C:\Program Files\nodejs\node.exe" "C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js" "start"
19 error node v7.8.0
20 error npm v4.2.0
21 error code ELIFECYCLE
22 error errno 1
23 error ga-dev-tools# start: gulp watch
23 error Exit status 1
24 error Failed at the ga-dev-tools# start script 'gulp watch'.
24 error Make sure you have the latest version of node.js and npm installed.
24 error If you do, this is most likely a problem with the ga-dev-tools package,
24 error not with npm itself.
24 error Tell the author that this fails on your system:
24 error gulp watch
24 error You can get information on how to open an issue for this project with:
24 error npm bugs ga-dev-tools
24 error Or if that isn't available, you can get their info via:
24 error npm owner ls ga-dev-tools
24 error There is likely additional logging output above.
25 verbose exit [ 1, true ]