javascript - debugging npm ERR! code ELIFECYCLE npm ERR! errno 1 - Stack Overflow

admin管理员组

文章数量:1318979

Asking for an advise on how to debug this piler error:

npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! ******@1.1.0 dev: `NODE_ENV=development ts-node ./src/server.ts`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the ******@1.1.0 dev script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A plete log of this run can be found in:

this appears when running ts-node ./src/server.ts or node build/server.js

tsc works without errors.

tsconfig.json:

{
   "pilerOptions": {
      "lib": [
         "es2018",
         "dom",
         "esnext.asynciterable"
      ],
      "target": "es2018",
      "module": "monjs",
      "outDir": "build",
      "emitDecoratorMetadata": true,
      "experimentalDecorators": true,
      "esModuleInterop": true,
      "sourceMap": false,
      "rootDirs": ["src", "../shared"]
//      "rootDir": "src"
   },
   "exclude": [
      "node_modules",
      "**/*.spec.ts",
      "**/*.test.ts"
   ],
   "references": [
      { "path": "../shared" }
   ]
}

I did made some changes in tsconfig which i suppose cause some imports to fail, however the codebase is huge and i really need some pointers to the exact lines in code which caused the error. especially confusing the tsc runs without errors.

UPDATE:

The issue was with some imports and fixed, However facing similar one again. Know the reason of the current issue - for some reason the imports from shared project (as in here .html) are not loaded (despite that they are working in other modules and tsconfig.json is the same with other modules). no particular error, just this npm ERR! code ELIFECYCLE npm ERR! errno 1.

Question:

However the main question of this topic is not the solution of the particularly this problem, but how to debug this kind of import problems where all available log is basically npm ERR! code ELIFECYCLE npm ERR! errno 1. I am facing this kind of issues periodically and every time it takes a lot of time to resolve since the only way to debug i know about is to ment chunks of code which might be associated with the possibly failed imports and sometimes this process could take hours.

Asking for an advise on how to debug this piler error:

npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! ******@1.1.0 dev: `NODE_ENV=development ts-node ./src/server.ts`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the ******@1.1.0 dev script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A plete log of this run can be found in:

this appears when running ts-node ./src/server.ts or node build/server.js

tsc works without errors.

tsconfig.json:

{
   "pilerOptions": {
      "lib": [
         "es2018",
         "dom",
         "esnext.asynciterable"
      ],
      "target": "es2018",
      "module": "monjs",
      "outDir": "build",
      "emitDecoratorMetadata": true,
      "experimentalDecorators": true,
      "esModuleInterop": true,
      "sourceMap": false,
      "rootDirs": ["src", "../shared"]
//      "rootDir": "src"
   },
   "exclude": [
      "node_modules",
      "**/*.spec.ts",
      "**/*.test.ts"
   ],
   "references": [
      { "path": "../shared" }
   ]
}

I did made some changes in tsconfig which i suppose cause some imports to fail, however the codebase is huge and i really need some pointers to the exact lines in code which caused the error. especially confusing the tsc runs without errors.

UPDATE:

The issue was with some imports and fixed, However facing similar one again. Know the reason of the current issue - for some reason the imports from shared project (as in here https://www.typescriptlang/docs/handbook/project-references.html) are not loaded (despite that they are working in other modules and tsconfig.json is the same with other modules). no particular error, just this npm ERR! code ELIFECYCLE npm ERR! errno 1.

Question:

However the main question of this topic is not the solution of the particularly this problem, but how to debug this kind of import problems where all available log is basically npm ERR! code ELIFECYCLE npm ERR! errno 1. I am facing this kind of issues periodically and every time it takes a lot of time to resolve since the only way to debug i know about is to ment chunks of code which might be associated with the possibly failed imports and sometimes this process could take hours.

• javascript
• node.js
• typescript
• npm

Share Improve this question Follow edited Oct 18, 2019 at 4:19 user1935987 asked Oct 16, 2019 at 4:57 user1935987user1935987 3,3471212 gold badges6363 silver badges113113 bronze badges 13

• stackoverflow./questions/42308879/npm-err-code-elifecycle – nayakam Commented Oct 16, 2019 at 5:27
• yeah i tried to follow suggestions from there, doesn't help. – user1935987 Commented Oct 16, 2019 at 5:30
• If you're trying that from windows, it won't work. Use the package cross-env to do that – darklightcode Commented Oct 16, 2019 at 6:41
• 1 Most of the time the console output before this output defines the error. But is there also nothing have a look in the log file which npm generates on error. The location is also display after "npm ERR! A plete log of this run can be found in:" – Mert Commented Oct 21, 2019 at 14:15
• 1 There is no tool for debuting to pilation. They have that in theirs roadmap, but it is yet to be stared to be worked on. – Akxe Commented Oct 24, 2019 at 22:56

 |  Show 8 more ments

4 Answers 4

Sorted by: Reset to default 4

I solved this problem first delete to package-lock.json write console - npm test
(if there isn't any problem in npm installing probably problem is in server)

• npm install -g serve
• npm run build

the problem is solved.. if you want to use your local you can enter

• serve -s build thats all- Good Luck :)

I would start with debugging the piled script (not minified though) because it removes some intermediate steps between your input and your results. There are multiple methods I tend to debug these issues:

• First I remend experimenting with NODE_DEBUG flags like: NODE_DEBUG=module node build/server.js if you suspect the issue is with module loading.
• You can try node --inspect-brk build/server.js and starting an inspector to step through it (e.g. in Chrome). This is most helpful if your code actually has managed to load, but can sometimes help with custom loaders.

As you have stated, the logs are not very detailed, so I would not invest energy into finding out how to debug an undetailed log file, but rather I would find out how to modify my project so that it does some more detailed logging, after each major step, so if it fails at some point, you will see what was successfully executed, what states it ran through and you will not see the logging that you have planned from the point of crashing.

based on @Porcellus answer, was able to fix this issues with NODE_DEBUG=* flag => shown a plete stacktrace of missing modules.

本文标签： javascriptdebugging npm ERR code ELIFECYCLE npm ERR errno 1Stack Overflow