Normalize paths for windows dev server
Open
Nobody has claimed this yet.
bug
v2
windows
- Dominant language
- TypeScript
- Stars
- 11.2k
- Forks
- 899
- Avg merge
- 2d 24m
- Merged PRs (30d)
- 40
Description
Linked issues:
- https://github.com/nuxt/nuxt.js/issues/15249
- https://github.com/nuxt-modules/turnstile/issues/85
- https://github.com/nuxt-modules/html-validator/issues/232
They were fixed by https://github.com/unjs/nitro/pull/732 and https://github.com/unjs/nitro/pull/733 but since fixes introduced new issues (https://github.com/unjs/nitro/issues/808), reverting on 2.x edge until finding a new solution.
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 reviewing the linked Nitro PRs #732 and #733, the resulting issue #808, and the related issues listed in the description. Trace the current 2.x edge Windows dev-server path behavior and establish a replacement that resolves the linked reports without reintroducing the regressions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100