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

Doesn't like having a CLI name that's different to the package name #29

Open
adam-lynch opened this issue Mar 2, 2020 · 2 comments
Open

Comments

@adam-lynch
Copy link

It took me way too long to realise that you can do this in your package.json:

  "name": "@org/package-name",
  "bin": {
    "cli-name": "./bin/cli.js"
  }

So it would help to document that in the README.md first of all.

Everything works then; i.e. you can use cli-name in dev and prod to run the CLI. However, pastel dev still shows the package name;

Development mode

Pastel watches your "commands" directory for changes and rebuilds application
when needed. After first successful build Pastel will also link your CLI for
you, so feel free to run your command right away:

$ @org/package-name --help

Now go create some beautiful CLI!
@matthewlynch
Copy link

You saved me a world of trouble, thanks!

@adam-lynch
Copy link
Author

You're welcome cousin 👍

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