[v2] Block plugin installation if compatibility is not stated
Open
Nobody has claimed this yet.
⏱ Status: Planned
❣️ Priority: High
- Dominant language
- TypeScript
- Stars
- 44.7k
- Forks
- 3.6k
- Avg merge
- 21m
- Merged PRs (30d)
- 1
Description
Many plugins will break with the release of v2, to prevent users from suffering from incompatible plugins and their errors/slowdowns, we should block installation/loading if they do not specify a certain tag in their package.json file. That tag could be something like
requiresHyperVersion: >2,
Discuss!
Contributor guide
No contributing guide indexed for this repository
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
Review the issue discussion and the plugin installation/loading paths associated with package.json compatibility metadata. First clarify the compatibility tag format and the intended behavior for plugins without it; done means the agreed v2 policy is specified and consistently enforced.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- cli, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100