[NextJS] Detecting middleware in installation
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 197
- Forks
- 51
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 94
Description
Sometimes users have middleware installed, and the /ingest route might get transformed / changed.
The AI should detect this and modify the middleware accordingly if it notices that middleware is present.
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
Start by tracing the installation flow that handles the /ingest route and look for where existing middleware can be detected. Done means the wizard notices middleware, accounts for transformations of /ingest, and modifies the middleware accordingly without disrupting installation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- next.js, typescript
- Domain
- tooling, web-dev
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100