nodejs / nodejs/node-addon-api
Considerations for the next major release
Open
Nobody has claimed this yet.
never-stale
SemVer-major
- Dominant language
- C++
- Stars
- 2.4k
- Forks
- 499
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 2
Description
Breaking changes:
- remove legacy except/no-except.gypi files.
- Remove nothing.c.
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 legacy except/no-except.gypi files and nothing.c named in the issue, then check how they are referenced by the project’s build and release setup. Done means the obsolete files and their references are removed without breaking the next major release.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, nodejs
- Domain
- build-system, release
- Issue type
- Refactor
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100