harness / harness/backstage-plugins
[Feat]: Migrate Plugin to new backstage frontend system
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- TypeScript
- Stars
- 39
- Forks
- 30
- PR merge metrics
- No merged PRs in 30d
Description
🔖 Feature description
Please update the harness plugin to be compatible with the new Backstage Frontend System.
🎤 Context
Backstage released a new frontend system for plugins recently.
When I installed the plugin I got this message:
This package's metadata does not indicate feature type information (in exports.backstage nor backstage.features) and may not be compatible with Portal.
Peer dependency is available in Portal at version 18.3.1, which does not satisfy the peer dependency version range. This may result in errors or inconsistent behavior. Please report this issue to the package owner.
react@"^16.13.1 || ^17.0.0"
✌️ Possible Implementation
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
No file, test, or entry point is named in the issue. Start with the linked Backstage frontend-system migration guide, then locate the harness plugin's frontend integration and package metadata; done means it is compatible with the new system and no longer reports the shown React peer-dependency or feature-type warnings.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- react, typescript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100