NativeScript / NativeScript/nativescript-cli
ns clean - should remove yarn.lock if the package manager for the project is yarn
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.
When you run ns clean on a project that uses yarn as the package manager, the CLI still tries to remove a package-lock.json instead of yarn.lock
Describe the solution you'd like
If the package manager of the project is yarn, then ns clean should attempt to remove yarn.lock if it exists.
Describe alternatives you've considered
As an alternative, the developer could be prompted if they wish to remove yarn.lock or package-lock.json.
Anything else?
No response
Please accept these terms
- I have searched the existing issues as well as StackOverflow and this has not been posted before
- I agree to follow this project's Code of Conduct
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 ns clean command and how it determines the project's package manager. Verify the cleanup behavior for Yarn projects and confirm completion by ensuring yarn.lock is targeted when present instead of package-lock.json; add or run the relevant cleanup tests if they are found.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100