npm build error about snaily-cadv3 HOT 11 CLOSED

@ItsSimko try re-installing the CAD to your documents/desktop folder. npm doesn't always have the correct permissions to install directly to the Users folder/C Drive

from snaily-cadv3.

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:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js',
1 verbose cli 'start'
1 verbose cli ]
2 info using [email protected]
3 info using [email protected]
4 verbose run-script [ 'prestart', 'start', 'poststart' ]
5 info lifecycle [email protected]prestart: [email protected]
6 info lifecycle [email protected]start: [email protected]
7 verbose lifecycle [email protected]start: unsafe-perm in lifecycle true
8 verbose lifecycle [email protected]start: PATH: C:\Program Files\nodejs\node_modules\npm\node_modules\npm-lifecycle\node-gyp-bin;C:\Users\Administrator\Documents\snaily-cadv3\node_modules.bin;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0;C:\Windows\System32\OpenSSH;C:\Program Files\nodejs;C:\Program Files\Git\cmd;C:\Users\Administrator\AppData\Local\Microsoft\WindowsApps;;C:\Users\Administrator\AppData\Local\Programs\Microsoft VS Code\bin;C:\Users\Administrator\AppData\Roaming\npm
9 verbose lifecycle [email protected]start: CWD: C:\Users\Administrator\Documents\snaily-cadv3
10 silly lifecycle [email protected]start: Args: [
10 silly lifecycle '/d /s /c',
10 silly lifecycle 'npm run translation:generate && npm run build && cross-env NODE_ENV=production node dist/server.js'
10 silly lifecycle ]
11 silly lifecycle [email protected]start: Returned: code: 3221225725 signal: null
12 info lifecycle [email protected]start: Failed to exec start script
13 verbose stack Error: [email protected] start: npm run translation:generate && npm run build && cross-env NODE_ENV=production node dist/server.js
13 verbose stack Exit status 3221225725
13 verbose stack at EventEmitter. (C:\Program Files\nodejs\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:\Program Files\nodejs\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 [email protected]
15 verbose cwd C:\Users\Administrator\Documents\snaily-cadv3
16 verbose Windows_NT 10.0.17763
17 verbose argv "C:\Program Files\nodejs\node.exe" "C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js" "start"
18 verbose node v14.16.1
19 verbose npm v6.14.12
20 error code ELIFECYCLE
21 error errno 3221225725
22 error [email protected] start: npm run translation:generate && npm run build && cross-env NODE_ENV=production node dist/server.js
22 error Exit status 3221225725
23 error Failed at the [email protected] start script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 3221225725, true ]

This is the errors I get now.

from snaily-cadv3.

Never seen this before. I’ll need to look into it tomorrow when I wake up

from snaily-cadv3.

Thank you, any help will be apreciated.

from snaily-cadv3.

@ItsSimko are you using the .env file or using the config.ts?

from snaily-cadv3.

config.ts

from snaily-cadv3.

Can you try removing the following folders and files

• dist/
• node_modules/
• .next/
• package-lock.json

Then run npm install again. Then start the CAD

from snaily-cadv3.

Okay, so I didn't have some of these folders, upon trying to build when I deleted package-lock.json it prompt me that my npm was outdated. One update later and I have none of the errors I had before. However, now I am getting different errors.

About how much ram does this CAD use? as I think it is a ram issue on my box as I am running a fairly low ram box.

from snaily-cadv3.

When building it can take a bit (sometimes), but when started it shouldn't take too much. So yeh, It can be a RAM issue.

from snaily-cadv3.

Alright, looks like it is a ram issue after more testing. Thanks for the help cant wait to use this for my community! :)

from snaily-cadv3.

Yep, no problem!

from snaily-cadv3.