thim81 / thim81/openapi-format
Consider turning public API synchronous and splitting away Node.js specific functionality
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 177
- Forks
- 29
- Avg merge
- 3d 13h
- Merged PRs (30d)
- 1
Description
Turning the core library into pure JS that can be safely used in browser or Node.js without polyfills or warnings. Keeping Node.js functionality to a separate export or to the CLI only.
This can also possibly make the API synchronous, which will make it easier to use in some places.
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
The issue names no files, tests, or entry points to begin with. First clarify whether the public API should become synchronous and how Node.js functionality should be separated; done should include an agreed browser-safe core API and a defined location for Node.js or CLI behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- cli, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100