Default handler for `.well-known/appspecific/com.chrome.devtools.json`
Open
Nobody has claimed this yet.
dev
enhancement
v2
- Dominant language
- TypeScript
- Stars
- 11.2k
- Forks
- 899
- Avg merge
- 2d 24m
- Merged PRs (30d)
- 40
Description
Describe the feature
Context: https://github.com/nuxt/nuxt/pull/32084 (docs)
Additional information
- Would you be willing to help implement this feature?
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
Start by reading the linked Nuxt pull request and the referenced design document to determine the intended behavior for .well-known/appspecific/com.chrome.devtools.json. Then locate Nitro's existing handling for well-known paths and identify the relevant tests or entry points; done means the requested default handler behavior is implemented and covered by tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nuxt, typescript
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100