rivet-dev / rivet-dev/dynamic-apps
Conformance: path.win32 APIs not implemented in sandbox
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- TypeScript
- Stars
- 1k
- Forks
- 51
- Avg merge
- 6m
- Merged PRs (30d)
- 13
Description
Upstream Node.js path tests check both path.posix and path.win32 behavior. Our path polyfill only implements POSIX semantics. Tests that call path.win32.* fail.
Tracked via conformance test exclusions (category: implementation-gap).
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 with the conformance tests referenced in the issue and trace the sandbox's path polyfill entry point. Run the excluded upstream Node.js path tests for path.win32, then confirm that the path.win32.* cases pass alongside the existing path.posix behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js, typescript
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100