Create bindings non-invasively/non-destructively? about node-addon-examples HOT 1 CLOSED

This is probably a structure you should strive for anyway. Most of the examples out there already like libxml and leveldown are wrapping existing libraries in node/v8 compatible code so they have that structure implicitly. Keeping your application code pure and adding just a wrapper layer is a nice way to separate concerns and make it more portable if it ever needs to be. Consider structuring the code where there's a "library" and a "wrapper" that sit separately and the dependency is only from the wrapper to the library and not the other way around.

For most of my addons, I'm extending something that already exists so I'm only ever writing wrapper code and don't need the portability of having an extra layer but if I was starting with something fresh then I'd absolutely consider separating it out.

from node-addon-examples.