Adding Support for a Node Release - node-webrtc/node-webrtc GitHub Wiki
What is "Support"
"Support" for a particular Node release means
- node-webrtc builds against the particular release, and
- node-webrtc ships binaries for the particular release.
In the past, we had to build distinct binaries for nearly every Node version we planned to support. With the advent of N-API, we can thankfully ship 1 binary targeting many different Node versions. Nevertheless, occasionally there have been bugs in the N-API implementation from Node version to Node version; and so this necessitates testing.
When to Add Support for a Node Release
We should add support for a Node release when created and our CI systems support it.
How to Add Support for a Node Release
1. Update CI
Travis CI, CircleCI, and AppVeyor should all be updated to build against the new Node release. The files in question are
2. Build and Fix Any Problems
Self-explanatory…
engines
in package.json
3. Update See the NPM documentation on engines
. It should list supported Node releases.
4. Update CHANGELOG.md and Release
Support for a new Node release is a new feature; therefore, list it in CHANGELOG.md and release a new minor version.