backstage / backstage/community-plugins
๐ airbrake: http-proxy-middleware v3 migration
- Dominant language
- TypeScript
- Stars
- 422
- Forks
- 697
- Avg merge
- 2d 6h
- Merged PRs (30d)
- 286
Description
### Plugin Name
airbrake
### ๐ Description
We aren't able to use v3 of `http-proxy-middleware` as it requires manual migration changes.
Renovate PR: https://github.com/backstage/community-plugins/pull/406
Migration details: https://github.com/chimurai/http-proxy-middleware/blob/master/MIGRATION.md#pathrewrite-potential-behavior-change
### ๐ Expected behavior
We should be able to up grade to v3 of `http-proxy-middleware`
### ๐ Actual Behavior with Screenshots
We are not able to up grade to v3 of `http-proxy-middleware`
### ๐ Reproduction steps
Try to upgrade the airbrake plugin to v3 of `http-proxy-middleware`
Notice: there are errors.
### ๐ Provide the context for the Bug.
We need to keep our dependencies up to date.
### ๐ Have you spent some time to check if this bug has been raised before?
- [X] I checked and didn't find similar issue
### ๐ข Have you read the Code of Conduct?
- [X] I have read the [Code of Conduct](https://github.com/backstage/community-plugins/blob/main/CODE_OF_CONDUCT.md)
### Are you willing to submit PR?
No, I don't have time to work on this right now
Contributor guide
Research direction
Locate the airbrake plugin code that uses http-proxy-middleware and read the linked v3 migration guidance, especially the pathRewrite behavior change. Reproduce the upgrade errors, update the affected usage, and run the plugin's existing checks to confirm the dependency can be upgraded without errors.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js, typescript
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100