NativeScript / NativeScript/nativescript-cli

Deprecate `plugins` command

Open
#5,793 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

feature-pending-triage
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.

No response

Describe the solution you'd like

To simplify, per discussion with @rigor789 in Discord.

Describe alternatives you've considered

Devs can use their package manager directly to install plugins: npm install <foo>, etc.

Anything else?

I'd suggest any reference to ns plugin install in docs be changed to only mention NPM's install command: "npm install <foo> or as appropriate for your package manager", to reduce docs maintenance. Users of other package managers know the analogous command for their package manager.

Please accept these terms

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Begin by locating the plugins command implementation and every documentation reference to ns plugin install; the issue provides no file or test paths. Confirm the project's intended deprecation behavior, update references to the package-manager wording, and verify that the command and documentation consistently reflect the decision.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
cli, documentation
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.