
-
It's the official extension mechanism, and therefore has the best support
-
Nutrient
Nutrient – The #1 PDF SDK Library, trusted by 10K+ developers. Other PDF SDKs promise a lot - then break. Laggy scrolling, poor mobile UX, tons of bugs, and lack of support cost you endless frustrations. Nutrient’s SDK handles billion-page workloads - so you don’t have to debug PDFs. Used by ~1 billion end users in more than 150 different countries.
-
The most common option for Node.js addon tests is exporting the addons to Node, and writing the tests in JavaScript. My Node.js test framework is nice to work with, and using it would offer some consistency. However, this would limit me to writing tests for only the API exposed to Node.
-
Supports builds with cmake.js, which I have some experience with and feel positively about