-
Notifications
You must be signed in to change notification settings - Fork 32
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
On my local machine i have problems to run the dojo "npm run build" command, please help, on other machines it just runs fine #448
Comments
@adylol thank you for the issue; we've tried to replicate this issue on a windows environment but have had no luck. You say that you can build your projects on other machines, it leads me to believe it's something related to this machines specific setup. I'll leave this issue open for a few days so if you manage to find any further information you can update it. |
Thanks for your help! I reinstalled again node.js with the additional tools option and restarted the system, |
Hi Anthony,
Thanks for your response!
I reinstalled again node.js with the additional tools option and restarted the system,
than it magically worked.. I guess, there was something wrong with the Windows PATH variable, since dojo build complaeined about installing dojo build locally (without -g option)
which I did not do.
I will put this finding also into the issue, that was created.
Again thanks a lot contacting me.
Andreas
Von: Anthony Gubler [mailto:notifications@github.com]
Gesendet: Mittwoch, 13. Januar 2021 11:22
An: dojo/cli-build-app <cli-build-app@noreply.github.com>
Cc: adylol <lorenz@lp-it.de>; Mention <mention@noreply.github.com>
Betreff: Re: [dojo/cli-build-app] On my local machine i have problems to run the dojo "npm run build" command, please help, on other machines it just runs fine (#448)
<https://github.com/adylol> @adylol thank you for the issue; we've tried to replicate this issue on a windows environment but have had no luck. You say that you can build your projects on other machines, it leads me to believe it's something related to this machines specific setup. I'll leave this issue open for a few days so if you manage to find any further information you can update it.
—
You are receiving this because you were mentioned.
Reply to this email directly, <#448 (comment)> view it on GitHub, or <https://github.com/notifications/unsubscribe-auth/ACWPMOQ5PXN3XBVX2N7BVIDSZVX5VANCNFSM4WASFNSQ> unsubscribe.
|
Closing as I think this worked (eventually) |
I tried reinstalling npm/node build tools chocolately, but it does not work. the app gets created with dojo create app --name hello-world, but can not be built.
The error trace gives no hints where to look.
0 info it worked if it ends with ok
1 verbose cli [
1 verbose cli 'C:\Program Files\nodejs\node.exe',
1 verbose cli 'C:\Users\lorenz\AppData\Roaming\npm\node_modules\npm\bin\npm-cli.js',
1 verbose cli 'run',
1 verbose cli 'build'
1 verbose cli ]
2 info using npm@6.14.10
3 info using node@v14.15.4
4 verbose run-script [ 'prebuild', 'build', 'postbuild' ]
5 info lifecycle hello-world3@1.0.0
prebuild: hello-world3@1.0.0build: hello-world3@1.0.06 info lifecycle hello-world3@1.0.0
7 verbose lifecycle hello-world3@1.0.0
build: unsafe-perm in lifecycle truebuild: PATH: C:\Users\lorenz\AppData\Roaming\npm\node_modules\npm\node_modules\npm-lifecycle\node-gyp-bin;E:\lorenz\dojo-cli\dojo-cli-hello-world\hello-world3\node_modules.bin;C:\Python39\Scripts;C:\Python39;C:\Users\lorenz\AppData\Local\Programs\Python\Python37-32;C:\Program Files (x86)\Common Files\Oracle\Java\javapath;C:\Program Files\Microsoft MPI\Bin;C:\Program Files (x86)\Intel\iCLS Client;C:\Program Files\Intel\iCLS Client;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0;C:\Program Files (x86)\NVIDIA Corporation\PhysX\Common;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:\Program Files\Microsoft SQL Server\120\Tools\Binn;C:\Program Files\Microsoft SQL Server\130\Tools\Binn;C:\Program Files\Git\cmd;C:\Program Files\Microsoft\Web Platform Installer;C:\Program Files (x86)\Microsoft SQL Server\110\DTS\Binn;C:\Program Files (x86)\Microsoft SQL Server\120\DTS\Binn;C:\Program Files (x86)\Microsoft SQL Server\130\DTS\Binn;C:\Program Files\dotnet;C:\Program Files (x86)\GtkSharp\2.12\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0;C:\WINDOWS\System32\OpenSSH;C:\Program Files (x86)\Android\android-sdk\tools;C:\Program Files (x86)\Android\android-sdk\platform-tools;C:\Users\lorenz\AppData\Local\Android\sdk\platform-tools;C:\Program Files\Java\jdk1.8.0_152\bin;C:\Program Files (x86)\Microsoft SQL Server\140\Tools\Binn;C:\Program Files\Microsoft SQL Server\140\Tools\Binn;C:\Program Files (x86)\Microsoft SQL Server\140\DTS\Binn;C:\Program Files\Microsoft SQL Server\140\DTS\Binn;C:\Program Files\Microsoft SQL Server\Client SDK\ODBC\130\Tools\Binn;C:\Program Files (x86)\Microsoft SQL Server\Client SDK\ODBC\130\Tools\Binn;C:\Program Files (x86)\Microsoft SQL Server\140\Tools\Binn\ManagementStudio;C:\Program Files (x86)\Microsoft SQL Server\130\Tools\Binn;C:\Program Files\Microsoft SQL Server\130\DTS\Binn;C:\Program Files\Intel\WiFi\bin;C:\Program Files\Common Files\Intel\WirelessCommon;C:\Program Files\Microsoft VS Code\bin;C:\Program Files\Microsoft SQL Server\Client SDK\ODBC\170\Tools\Binn;C:\ProgramData\chocolatey\bin;C:\Users\lorenz\AppData\Roaming\npm;C:\Program Files\nodejs8 verbose lifecycle hello-world3@1.0.0
9 verbose lifecycle hello-world3@1.0.0
build: CWD: E:\lorenz\dojo-cli\dojo-cli-hello-world\hello-world3build: Args: [ '/d /s /c', 'dojo build --mode dist' ]10 silly lifecycle hello-world3@1.0.0
11 silly lifecycle hello-world3@1.0.0
build: Returned: code: 1 signal: nullbuild: Failed to exec build script12 info lifecycle hello-world3@1.0.0
13 verbose stack Error: hello-world3@1.0.0 build:
dojo build --mode dist
13 verbose stack Exit status 1
13 verbose stack at EventEmitter. (C:\Users\lorenz\AppData\Roaming\npm\node_modules\npm\node_modules\npm-lifecycle\index.js:332:16)
13 verbose stack at EventEmitter.emit (events.js:315:20)
13 verbose stack at ChildProcess. (C:\Users\lorenz\AppData\Roaming\npm\node_modules\npm\node_modules\npm-lifecycle\lib\spawn.js:55:14)
13 verbose stack at ChildProcess.emit (events.js:315:20)
13 verbose stack at maybeClose (internal/child_process.js:1048:16)
13 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:288:5)
14 verbose pkgid hello-world3@1.0.0
15 verbose cwd E:\lorenz\dojo-cli\dojo-cli-hello-world\hello-world3
16 verbose Windows_NT 10.0.19041
17 verbose argv "C:\Program Files\nodejs\node.exe" "C:\Users\lorenz\AppData\Roaming\npm\node_modules\npm\bin\npm-cli.js" "run" "build"
18 verbose node v14.15.4
19 verbose npm v6.14.10
20 error code ELIFECYCLE
21 error errno 1
22 error hello-world3@1.0.0 build:
dojo build --mode dist
22 error Exit status 1
23 error Failed at the hello-world3@1.0.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 ]
The text was updated successfully, but these errors were encountered: