Node.js Persistence
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1.1k
- Forks
- 92
- Avg merge
- 11h 2m
- Merged PRs (30d)
- 2
Description
Continuing discussion from https://github.com/sqlite/sqlite-wasm/pull/48
Proposed solutions:
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 reading pull request #48 and its linked discussion, including the Node.js VFS and OPFS Polyfill proposals. Compare those approaches for Node.js persistence and clarify which one should be pursued; done means an agreed approach is implemented and the persistence behavior is verified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js, wasm
- Domain
- databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100