Node.js Bindings
- Dominant language
- C++
- Stars
- 16.7k
- Forks
- 1.6k
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 126
Description
We have historically maintained bindings in Node that wrapped our C bindings. However, it was initially developed for an older version of Node, and as time went on, it became incompatible with modern versions of the language. At this point, it is not particularly useful for Node users due to those incompatibilities. It also could probably benefit from some of the new Node features that have been developed in the intervening releases. As a result, it would seem like we should remove the Node bindings until such time as a suitable replacement is available. If there is demand for such a binding, the old Node bindings will still exist in history, so our previous work could plausibly be used as a jumping off point for someone who wanted to create their own.
Contributor guide
Research direction
Start by locating the existing Node.js bindings and the C bindings they wrap, then inspect how the Node component is connected to the project’s build and release paths. The issue’s intended outcome is removal of the obsolete Node bindings, with no replacement specified; verify that the remaining C/C++ project still builds and that no Node-specific references remain.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, cpp, node.js
- Domain
- api, backend
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100