NativeScript / NativeScript/nativescript-cli
Detect when the CLI is installed as a dependency and show an user-friendly error
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1.1k
- Forks
- 204
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 8
Description
Is your feature request related to a problem? Please describe.
It's easy to forget --global or --save-dev when installing/updating the NativeScript CLI. This leads to a strange fail in the native build of the app.
Describe the solution you'd like
The CLI could detect such cases and show an error describing the problematic state and possible solutions.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the CLI installation and native build entry points to identify how dependency installation differs from global or development installation. Define the detectable problematic states and the user-facing error before checking the existing CLI test structure; done means the CLI reports the state and suggested installation solutions instead of failing later during the native build.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100