Vincent Weevers
Vincent Weevers
If you use Node-API (and you should) then you only need a single prebuild because Node-API provides forward-compatibility (i.e. it'll work on the current Node.js version and every future version)....
Agreed. We did that in `abstract-level` but forgot to copy it to here. PR welcome.
We might get lucky if we just bump the version [here](https://github.com/vweevers/docker-pull/blob/2cca4eea5afb282791835946b3a183406b3b5fe3/index.js#L15) and if the subset of the API that we use did not have breaking changes. Otherwise, we'll have to...
At quick glance, 1.24 is compatible with the API that we use. Could you try that out?
> As of @vweevers/docker-pull, it accepts a version option. Yes, but I prefer to change the version there, so both modules benefit. Either way, we need someone to confirm that...
I'll go for #21 because it fixes both `docker-pull` and `docker-run` while #22 only fixes `docker-pull`. Thank you both!
Fixed in 5.1.1.
I don't think we need this PR, you can already pass `--no-napi` to override the default.
It's an old trick to tell Node.js (and bundlers that follow the same `require()` algorithm) to load an npm package instead of a core module. Might be an issue with...
> Is this still maintained? Very lightly. It's stable and does not need new features. Several of the contributors prefer [`prebuildify`](https://github.com/prebuild/prebuildify) & [`node-gyp-build`](https://github.com/prebuild/node-gyp-build). IMO it's time to deprecate `prebuild` and...