Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

build error #554

Closed
jiawulin001 opened this issue Feb 17, 2020 · 0 comments · Fixed by #556
Closed

build error #554

jiawulin001 opened this issue Feb 17, 2020 · 0 comments · Fixed by #556

Comments

@jiawulin001
Copy link

An error occurred while I was building xml2js:

D:\Code\node-xml2js>npm run build

> [email protected] build D:\Code\node-xml2js
> cake build

events.js:167
      throw er; // Unhandled 'error' event
      ^

Error: spawn coffee ENOENT
    at Process.ChildProcess._handle.onexit (internal/child_process.js:232:19)
    at onErrorNT (internal/child_process.js:407:16)
    at process._tickCallback (internal/process/next_tick.js:63:19)
    at Function.Module.runMain (internal/modules/cjs/loader.js:745:11)
    at startup (internal/bootstrap/node.js:279:19)
    at bootstrapNodeJSCore (internal/bootstrap/node.js:752:3)

Emitted 'error' event at:
    at Process.ChildProcess._handle.onexit (internal/child_process.js:238:12)
    at onErrorNT (internal/child_process.js:407:16)
    [... lines matching original stack trace ...]

npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] build: `cake build`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] 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!     C:\Users\jiawulin-pc\AppData\Roaming\npm-cache\_logs\2020-02-17T08_41_50_680Z-debug.log

I tried to execute the coffee -cw -o lib src command,It worked。
image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant