-
-
Notifications
You must be signed in to change notification settings - Fork 3.8k
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
couldnt make it work #1
Comments
here is another attempt: 0 info it worked if it ends with ok |
Seems like you are stuck at |
hi, before i try to run it i read installation part and did all of you regards. 2016-02-08 21:27 GMT+02:00 Artur Arseniev notifications@github.com:
|
Added support for colon in css class names
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
hi,
i followed the instructions of installation here is the error log i get;
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 'run',
1 verbose cli 'build' ]
2 info using npm@3.3.12
3 info using node@v5.5.0
4 verbose run-script [ 'prebuild', 'build', 'postbuild' ]
5 info lifecycle grapesjs@0.1.0
prebuild: grapesjs@0.1.0prebuild: no script for prebuild, continuing6 silly lifecycle grapesjs@0.1.0
7 info lifecycle grapesjs@0.1.0
build: grapesjs@0.1.0build: unsafe-perm in lifecycle true8 verbose lifecycle grapesjs@0.1.0
9 verbose lifecycle grapesjs@0.1.0
build: PATH: C:\Program Files\nodejs\node_modules\npm\bin\node-gyp-bin;C:\Users[UserName]\Documents\GitHub\grapesjs\node_modules.bin;C:\Windows\system32;C:\Windows;C:\Windows\system32\wbem;C:\ProgramData\Oracle\Java\javapath;C:\Program Files (x86)\NVIDIA Corporation\PhysX\Common;C:\Program Files\Microsoft\Web Platform Installer;C:\Program Files\Microsoft SQL Server\120\Tools\Binn;C:\Program Files (x86)\Windows Kits\8.1\Windows Performance Toolkit;C:\Program Files\Microsoft SQL Server\110\Tools\Binn;C:\Program Files (x86)\Microsoft SDKs\TypeScript\1.0;C:\Windows\System32\WindowsPowerShell\v1.0;C:\Program Files\Git\cmd;C:\Program Files\nodejs;C:\Users[UserName]\AppData\Roaming\npmbuild: CWD: C:\Users[UserName]\Documents\GitHub\grapesjs10 verbose lifecycle grapesjs@0.1.0
11 silly lifecycle grapesjs@0.1.0
build: Args: [ '/d /s /c', 'grunt build' ]build: Returned: code: 6 signal: null12 silly lifecycle grapesjs@0.1.0
13 info lifecycle grapesjs@0.1.0~build: Failed to exec build script
14 verbose stack Error: grapesjs@0.1.0 build:
grunt build
14 verbose stack Exit status 6
14 verbose stack at EventEmitter. (C:\Program Files\nodejs\node_modules\npm\lib\utils\lifecycle.js:232:16)
14 verbose stack at emitTwo (events.js:100:13)
14 verbose stack at EventEmitter.emit (events.js:185:7)
14 verbose stack at ChildProcess. (C:\Program Files\nodejs\node_modules\npm\lib\utils\spawn.js:24:14)
14 verbose stack at emitTwo (events.js:100:13)
14 verbose stack at ChildProcess.emit (events.js:185:7)
14 verbose stack at maybeClose (internal/child_process.js:821:16)
14 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:211:5)
15 verbose pkgid grapesjs@0.1.0
16 verbose cwd C:\Users[UserName]\Documents\GitHub\grapesjs
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" "run" "build"
19 error node v5.5.0
20 error npm v3.3.12
21 error code ELIFECYCLE
22 error grapesjs@0.1.0 build:
grunt build
22 error Exit status 6
23 error Failed at the grapesjs@0.1.0 build script 'grunt build'.
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 grapesjs package,
23 error not with npm itself.
23 error Tell the author that this fails on your system:
23 error grunt build
23 error You can get their info via:
23 error npm owner ls grapesjs
23 error There is likely additional logging output above.
24 verbose exit [ 1, true ]
The text was updated successfully, but these errors were encountered: