add back deno nodejs compatibility for backwards compatibility
Open
Nobody has claimed this yet.
v3
- Dominant language
- TypeScript
- Stars
- 11.2k
- Forks
- 899
- Avg merge
- 2d 24m
- Merged PRs (30d)
- 40
Description
add back deno nodejs compatibility for deno v1 backwards compatibility
previously nitro v2 added process, Buffer, global, etc. to globalThis when using deno-server but nitro v3 doesn't
it doesn't hurt if you bring this back
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 locating the deno-server adapter and any Nitro v2 implementation of Node.js compatibility. Check how process, Buffer, global, and related globals were added to globalThis, then verify that Deno v1 deployments expose the same compatibility without breaking current behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- deno, nodejs, typescript
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100