Thanks for your reply @nilzao. I have issues installing node in Ubuntu. On Windows, this is the error log:

In Terminal:

> wysiwyg@0.0.1 start F:\xampp\htdocs\xtest\architect
> cross-env-shell npm run dev

'cross-env-shell' is not recognized as an internal or external command,
operable program or batch file.
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! wysiwyg@0.0.1 start: `cross-env-shell npm run dev`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the wysiwyg@0.0.1 start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm WARN Local package.json exists, but node_modules missing, did you mean to install?

npm ERR! A complete log of this run can be found in:
npm ERR!     C:\Users\Daniel\AppData\Roaming\npm-cache\_logs\2020-08-18T11_44_50_579Z-debug.log

And the error log file:

0 info it worked if it ends with ok
1 verbose cli [
1 verbose cli   'B:\\nodejs\\node.exe',
1 verbose cli   'C:\\Users\\Daniel\\AppData\\Roaming\\npm\\node_modules\\npm\\bin\\npm-cli.js',
1 verbose cli   'start'
1 verbose cli ]
2 info using npm@6.14.8
3 info using node@v12.18.3
4 verbose run-script [ 'prestart', 'start', 'poststart' ]
5 info lifecycle wysiwyg@0.0.1~prestart: wysiwyg@0.0.1
6 info lifecycle wysiwyg@0.0.1~start: wysiwyg@0.0.1
7 verbose lifecycle wysiwyg@0.0.1~start: unsafe-perm in lifecycle true
8 verbose lifecycle wysiwyg@0.0.1~start: PATH: C:\Users\Daniel\AppData\Roaming\npm\node_modules\npm\node_modules\npm-lifecycle\node-gyp-bin;F:\xampp\htdocs\xtest\architect\node_modules\.bin;;%SYSTEMROOT%\System32\WindowsPowerShell\v1.0\;%SYSTEMROOT%\System32\OpenSSH\;C:\Program Files (x86)\Microsoft VS Code\bin;C:\Users\Daniel\AppData\Local\Microsoft\WindowsApps;F:\xampp\php;\;C:\Users\Daniel\AppData\Roaming\npm;;F:\php-sdk;F:\php-dev;B:\visualstudio2019\VC\bin;C:\Users\Daniel\.dotnet\tools;%USERPROFILE%\AppData\Local\Microsoft\WindowsApps;
9 verbose lifecycle wysiwyg@0.0.1~start: CWD: F:\xampp\htdocs\xtest\architect
10 silly lifecycle wysiwyg@0.0.1~start: Args: [ '/d /s /c', 'cross-env-shell npm run dev' ]
11 silly lifecycle wysiwyg@0.0.1~start: Returned: code: 1  signal: null
12 info lifecycle wysiwyg@0.0.1~start: Failed to exec start script
13 verbose stack Error: wysiwyg@0.0.1 start: `cross-env-shell npm run dev`
13 verbose stack Exit status 1
13 verbose stack     at EventEmitter.<anonymous> (C:\Users\Daniel\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.<anonymous> (C:\Users\Daniel\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:1021:16)
13 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:286:5)
14 verbose pkgid wysiwyg@0.0.1
15 verbose cwd F:\xampp\htdocs\xtest\architect
16 verbose Windows_NT 10.0.19041
17 verbose argv "B:\\nodejs\\node.exe" "C:\\Users\\Daniel\\AppData\\Roaming\\npm\\node_modules\\npm\\bin\\npm-cli.js" "start"
18 verbose node v12.18.3
19 verbose npm  v6.14.8
20 error code ELIFECYCLE
21 error errno 1
22 error wysiwyg@0.0.1 start: `cross-env-shell npm run dev`
22 error Exit status 1
23 error Failed at the wysiwyg@0.0.1 start script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 1, true ]

Any chance to make it work with Ext GPL or the local library?

Installation steps #1

Description

Metadata

Metadata

Assignees

Labels

Projects

Milestone

Relationships

Development

Issue actions