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

./node_modules/.bin/catalog build throws #408

Closed
safareli opened this issue Apr 20, 2018 · 4 comments
Closed

./node_modules/.bin/catalog build throws #408

safareli opened this issue Apr 20, 2018 · 4 comments

Comments

@safareli
Copy link

safareli commented Apr 20, 2018

$ ./node_modules/.bin/catalog build
/myproject/node_modules/args/lib/utils.js:317
      throw err;
      ^

Error: spawn catalog-build ENOENT
    at exports._errnoException (util.js:1020:11)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:197:32)
    at onErrorNT (internal/child_process.js:376:16)
    at _combinedTickCallback (internal/process/next_tick.js:80:11)
    at process._tickCallback (internal/process/next_tick.js:104:9)
    at Module.runMain (module.js:606:11)
    at run (bootstrap_node.js:383:7)
    at startup (bootstrap_node.js:149:9)
    at bootstrap_node.js:496:3
@jstcki
Copy link
Contributor

jstcki commented Apr 20, 2018

This seems to be related to #343. Upgrading Catalog to a newer version should fix your problem.

@safareli
Copy link
Author

I'm on recent version:

$  ./node_modules/.bin/catalog -v
3.5.2
$ ./node_modules/.bin/catalog start
/Users/safareli/myproject/node_modules/args/lib/utils.js:317
      throw err;
      ^

Error: spawn catalog-start ENOENT
    at exports._errnoException (util.js:1020:11)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:197:32)
    at onErrorNT (internal/child_process.js:376:16)
    at _combinedTickCallback (internal/process/next_tick.js:80:11)
    at process._tickCallback (internal/process/next_tick.js:104:9)
    at Module.runMain (module.js:606:11)
    at run (bootstrap_node.js:383:7)
    at startup (bootstrap_node.js:149:9)
    at bootstrap_node.js:496:3

While:

$ npm start

> @ start /Users/safareli/myproject
> catalog start


  Starting Catalog …

@jstcki
Copy link
Contributor

jstcki commented Apr 25, 2018

This seems to be a limitation of the args module which executes scripts from package.json instead of the subcommand files directly. When you run catalog start as an npm script, it works correctly because in the npm run context the scripts from package.json are available but otherwise not. I'm not sure what we can do to fix this other than document the issue somehow.

For reference: leo/args#69, leo/args#83

@jstcki
Copy link
Contributor

jstcki commented May 19, 2018

@safareli I'm closing this since there doesn't seem anything we can do about it at the moment. Feel free to ping me when the issue is resolved in args. Thanks!

@jstcki jstcki closed this as completed May 19, 2018
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

No branches or pull requests

2 participants