error E:\User\Documents\Work\nucleus-server\node_modules\sqlite3: Command failed. #98
Comments
|
I believe nucleus has deps that depends on a lower version of node (8 I believe) |
so should I install node 8 first? @b-zurg |
|
Yes, give that a try |
|
I installed nvm and change node version to 8.4.0, PS E:\User\Documents\Work\nucleus-server> yarn
yarn install v1.22.4
[1/4] Resolving packages...
success Already up-to-date.
Done in 0.97s.
PS E:\User\Documents\Work\nucleus-server> yarn dev
yarn run v1.22.4
$ concurrently --raw "npm run start:fe" "npm run start:server:dev" "npm run start:static"
> [email protected] start:fe E:\User\Documents\Work\nucleus-server
> webpack-dev-server --progress --profile --colors --quiet --open
> [email protected] start:server:dev E:\User\Documents\Work\nucleus-server
> nodemon --watch src --exec "npm run build:server && cross-env DEBUG=nucleus* npm run start:server:prod" -e ts
> [email protected] start:static E:\User\Documents\Work\nucleus-server
> make-dir .files && serve .files --port 9999 --silent
[nodemon] 1.12.1
[nodemon] to restart at any time, enter `rs`
[nodemon] watching: E:\User\Documents\Work\nucleus-server\src/**/*
[nodemon] starting `npm run build:server && cross-env DEBUG=nucleus* npm run start:server:prod`
> [email protected] build:server E:\User\Documents\Work\nucleus-server
> tsc && rm -rf lib/__spec__ lib/**/__spec__
10% building modules 2/4 modules 2 active ...\webpack\hot nonrecursive /^\.\/log$/
> [email protected] start:server:prod E:\User\Documents\Work\nucleus-server
> node lib/index.js
11% building modules 9/10 modules 1 active ...\Work\nucleus-server\public\index.tsx
[at-loader] Using [email protected] from typescript and "tsconfig.json" from E:\User\Documents\Work\nucleus-server\tsconfig.public.json.
nucleus Setting up server +0ms
nucleus Connecting to DB +3ms
sequelize deprecated String based operators are now deprecated. Please use Symbol based operators for better security, read more at http://docs.sequelizejs.com/manual/tutorial/querying.html#operators
node_modules\sequelize\lib\sequelize.js:236:13
nucleus Checking GPG key +2s
"--gpg: directory '/c/Users/Clark/.gnupg' created\ngpg: keybox '/c/Users/Clark/.gnupg/pubring.kbx' created\ngpg: no valid OpenPGP data found.\ngpg: Total number processed: 0\n"
nucleus Bad gpg key, invalid +432ms
GPG key is invalid or missing, you must provide "config.gpgSigningKey"
11% building modules 10/10 modules 0 activenpm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] start:server:prod: `node lib/index.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] start:server:prod 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! C:\Users\Clark\AppData\Roaming\npm-cache\_logs\2020-07-01T07_03_22_444Z-debug.log
11% building modules 10/11 modules 1 active ...ode_modules\webpack\buildin\module.js[nodemon] app crashed - waiting for file changes before starting...
50309ms building modules
71ms sealing
16ms optimizing
1ms basic module optimization
14ms module optimization
2ms advanced module optimization
3ms basic chunk optimization
11ms chunk optimization
3ms advanced chunk optimization
2ms module and chunk tree optimization
31ms module reviving
6ms module order optimization
10ms module id optimization
7ms chunk reviving
9ms chunk order optimization
61ms chunk id optimization
67ms hashing
47ms module assets processing
2694ms chunk assets processing
47ms additional chunk assets processing
1ms recording
1ms additional asset processing
13ms chunk asset optimization
260ms asset optimization
241ms emitting
[HPM] Error occurred while trying to proxy request /rest/config from 127.0.0.1:8888 to http://localhost:3030 (ECONNREFUSED) (https://nodejs.org/api/errors.html#errors_common_system_errors)
|
|
okay, I should add gpg into config.js |
|
Oh yeah. Honestly there should be an error message for that. It's so cryptic. I also kind of just use the docker image as I think there's certain deps that don't even build on later versions of Ubuntu for example. It's a solid protect but could use a refresh |
|
can I use nucleus as a nodejs module? but how? @b-zurg |
|
Do you have the option to run it as a docker container? That might be your fastest option. I haven't run nucleus on a non-docker environment for a little while. It's definitely possible but the dependencies really need to be upgraded. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
install nucleus manually, when I run
yarnthen get those errors. any helps? thanks :)The text was updated successfully, but these errors were encountered: