Vincent Weevers

Is it possible for you to move or copy `lib/` into `build/`? Because `prebuild >= 8.2.0` recursively collects artifacts in the `build/` folder (#238). With a matching `--include-dir` option you...

> This is due to nw-gyp [using an old version of gyp](https://github.com/nwjs/nw-gyp/blob/1eb5e1b0b45f7257bebd46d80877c915a5b77bb5/gyp/pylib/gyp/MSVSVersion.py#L421-L435) which doesn't have an entry for VS 2019. Unfortunately that project seems rather stale so I don't know...

@m4heshd Unlikely to get worked on. Several of us have [moved on](https://github.com/prebuild/prebuild-install#note) to [`prebuildify`](https://github.com/prebuild/prebuildify). Which can differentiate ARM versions. You might also like [`prebuildify-cross`](https://github.com/prebuild/prebuildify-cross) to cross-compile for ARM.

The problem there is that the `-u` in `prebuild -r napi -u` is short for `--upload` and thus overrides the rc value. So `prebuild -r napi` should work in this...

Yes, it would! It's been suggested before (https://github.com/prebuild/prebuild/issues/131#issuecomment-239383203). A PR is welcome. Not sure if we can do it without a breaking change.

Right, as a new option would not be breaking 👍

Two separate PRs are welcome: 1. Replace Travis (and Appveyor) with a GitHub Actions workflow, because our CI is currently broken and we'd like to test all of this. Also...

[N-API](https://nodejs.org/api/n-api.html) is the preferred way to achieve this. I don't think it's feasible or desirable to have `prebuild` support both N-API and custom ways of abi agnostic packages. You might...

Sorry, I misunderstood.

64-bit builds were fixed, 32-bit builds still fail. I don't use `cmake-js`. Could someone (who has opinions about https://github.com/cmake-js/cmake-js/issues/186#issuecomment-518150342 and https://github.com/cmake-js/cmake-js/issues/188) take over?