search

jerosoler / newpct-total

Descargas de Newpct to transmission
15 stars 1 forks source link

Problemas en la build #8

Closed alienboyxp closed 4 years ago

alienboyxp commented 6 years ago

Tengo este error al intentar ejecutar la build (npm run build) con la última version de Node.j sobre Mac OS Mojave... se te ocurre algo? 1000 Gracias!!!

nuxt build && backpack build

node[28934]: ../src/node_file.cc:893:void node::fs::Stat(const FunctionCallbackInfo &): Assertion (argc) == (4)' failed. 1: 0x1000623a3 node::Abort() [/usr/local/bin/node] 2: 0x1000622d5 node::PrintErrorString(char const*, ...) [/usr/local/bin/node] 3: 0x10006adbd node::fs::LStat(v8::FunctionCallbackInfo<v8::Value> const&) [/usr/local/bin/node] 4: 0x1002292a7 v8::internal::FunctionCallbackArguments::Call(v8::internal::CallHandlerInfo*) [/usr/local/bin/node] 5: 0x100228876 v8::internal::MaybeHandle<v8::internal::Object> v8::internal::(anonymous namespace)::HandleApiCallHelper<false>(v8::internal::Isolate*, v8::internal::Handle<v8::internal::HeapObject>, v8::internal::Handle<v8::internal::HeapObject>, v8::internal::Handle<v8::internal::FunctionTemplateInfo>, v8::internal::Handle<v8::internal::Object>, v8::internal::BuiltinArguments) [/usr/local/bin/node] 6: 0x100227f70 v8::internal::Builtin_Impl_HandleApiCall(v8::internal::BuiltinArguments, v8::internal::Isolate*) [/usr/local/bin/node] 7: 0xbf00bcfb7d sh: line 1: 28934 Abort trap: 6 nuxt build npm ERR! code ELIFECYCLE npm ERR! errno 134 npm ERR! newpct-total@1.0.0 build:nuxt build && backpack build` npm ERR! Exit status 134 npm ERR! npm ERR! Failed at the newpct-total@1.0.0 build 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! /var/root/.npm/_logs/2018-11-20T15_12_26_340Z-debug.log

Y este el log de debug: 0 info it worked if it ends with ok 1 verbose cli [ '/usr/local/bin/node', '/usr/local/bin/npm', 'run', 'build' ] 2 info using npm@6.4.1 3 info using node@v11.2.0 4 verbose run-script [ 'prebuild', 'build', 'postbuild' ] 5 info lifecycle newpct-total@1.0.0~prebuild: newpct-total@1.0.0 6 info lifecycle newpct-total@1.0.0~build: newpct-total@1.0.0 7 verbose lifecycle newpct-total@1.0.0~build: unsafe-perm in lifecycle true 8 verbose lifecycle newpct-total@1.0.0~build: PATH: /usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/Users/juanjoser/Desktop/Torrent/newpct-total/node_modules/.bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/A$ 9 verbose lifecycle newpct-total@1.0.0~build: CWD: /Users/juanjoser/Desktop/Torrent/newpct-total 10 silly lifecycle newpct-total@1.0.0~build: Args: [ '-c', 'nuxt build && backpack build' ] 11 silly lifecycle newpct-total@1.0.0~build: Returned: code: 134 signal: null 12 info lifecycle newpct-total@1.0.0~build: Failed to exec build script 13 verbose stack Error: newpct-total@1.0.0 build: nuxt build && backpack build 13 verbose stack Exit status 134 13 verbose stack at EventEmitter. (/usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/index.js:301:16) 13 verbose stack at EventEmitter.emit (events.js:182:13) 13 verbose stack at ChildProcess. (/usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14) 13 verbose stack at ChildProcess.emit (events.js:182:13) 13 verbose stack at maybeClose (internal/child_process.js:978:16) 13 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:265:5) 14 verbose pkgid newpct-total@1.0.0 15 verbose cwd /Users/juanjoser/Desktop/Torrent/newpct-total 16 verbose Darwin 18.2.0 17 verbose argv "/usr/local/bin/node" "/usr/local/bin/npm" "run" "build" 18 verbose node v11.2.0 19 verbose npm v6.4.1 20 error code ELIFECYCLE 21 error errno 134 22 error newpct-total@1.0.0 build: nuxt build && backpack build 22 error Exit status 134 23 error Failed at the newpct-total@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 [ 134, true ]

jerosoler commented 6 years ago

Prueba a borrar la carpeta node_modules y a borrar la cache de npm npm cache clean --force

Y otra vez: install dependencies npm install # Or yarn install Montando proyecto npm run build Lanzando servidor npm start

Si no prueba a ejecutar con npm run dev Haber si así funciona

Que versión de node tienes? nodejs -v

alienboyxp commented 6 years ago

Gracias por la rápida respuesta!!! he ido avanzando y solventando problemas y ahora en npm run build me da este error ERROR in ./.nuxt/client.js Module build failed (from ./node_modules/eslint-loader/index.js): TypeError: Cannot read property 'eslint' of undefined at Object.module.exports (/Users/juanjoser/Desktop/Torrent/newpct-total/node_modules/eslint-loader/index.js:148:18) @ multi ./.nuxt/client.js app[0]

FATAL Nuxt Build Error
la version de js es la 10 LTS

jerosoler commented 6 years ago

Mira dentro de la carpeta node_modules si esta la carpeta "eslint-loader" y "eslint" Si no instalalo. npm install eslint-loader eslint

Prueba si no ha instalar todas las dependencias del package.json

 "devDependencies": {
    "babel-eslint": "^7.2.3",
    "backpack-core": "^0.4.1",
    "eslint": "^4.3.0",
    "eslint-config-standard": "^10.2.1",
    "eslint-loader": "^1.9.0",
    "eslint-plugin-html": "^3.1.1",
    "eslint-plugin-import": "^2.7.0",
    "eslint-plugin-node": "^5.1.1",
    "eslint-plugin-promise": "^3.5.0",
    "eslint-plugin-standard": "^3.0.1"
  }
alienboyxp commented 6 years ago

Hola, si estan en el directorio que comentas e instale todas las dependencias del package.json pero sigue dando el mismo error... que rábia con las ganas que tenia de ver como funcionaba. Lanzando npm build dev retorna este error por si es de ayuda...

ERROR Failed to compile with 1 errors friendly-errors 15:27:48

Module build failed (from ./node_modules/eslint-loader/index.js): friendly-errors 15:27:48 TypeError: Cannot read property 'eslint' of undefined at Object.module.exports (/Users/juanjoser/Desktop/Torrent/newpct-total/node_modules/eslint-loader/index.js:148:18) friendly-errors 15:27:48 You may use special comments to disable some warnings. friendly-errors 15:27:48 Use // eslint-disable-next-line to ignore the next line. friendly-errors 15:27:48 Use / eslint-disable / to ignore all warnings in a file.

jerosoler commented 6 years ago

Que versión de nodejs utilizas? nodejs -v

alienboyxp commented 6 years ago

node -v v10.13.0

jerosoler commented 6 years ago

Hola, acabo de probar con una v10.13.0

Hazlo todo de nuevo pero en vez de hacer un npm install haz un npm update como te muestro abajo. 

#Download project
git clone https://github.com/jerosoler/newpct-total.git
# Entrar al directorio
cd newpct-total
# install dependencies
npm update
# Montando proyecto
npm run build
# Lanzando servidor
npm start # Or pm2 start npm --name="newpct" -- start
alienboyxp commented 6 years ago

Ahora siiii!!! Muchisimas gracias!!! Si puedo hacerte unas preguntas/sugerencias :)

jerosoler commented 6 years ago

Hola, Perfecto que te funcione.

Saludos

ibanana commented 5 years ago

conseguido no me preguntes como pero listo gracias de todas formas