Vincent Weevers
Vincent Weevers
I believe the (better) logic is in node-gyp nowadays, since https://github.com/nodejs/node-gyp/pull/1762. So there are a few options: 1. Use gyp-next's python code: [MSVSVersion.py](https://github.com/nodejs/gyp-next/blob/main/pylib/gyp/MSVSVersion.py). Not great because you'd then also have...
Sample `build/config.gypi`: ```json # Do not edit. File was generated by node-gyp's "configure" step { "target_defaults": { ... }, "variables": { ... "msbuild_path": "C:\\Program Files (x86)\\Microsoft Visual Studio\\2019\\Professional\\MSBuild\\Current\\Bin\\MSBuild.exe", } }...
The upcoming release will pin Babel to 5, to resolve these issues and so we can have hot reloading. We can't move to Babel 6 until [babel-plugin-react-transform#46](https://github.com/gaearon/babel-plugin-react-transform/issues/46) and [livereactload#78](https://github.com/milankinen/livereactload/issues/78) have...
Could you please elaborate?
Can you give an example of an arg/option where this is a problem?
Wouldn't `options[key]` be `true` in that case? 🤔 Perhaps we should replace the `options` object with an `args` array. That way you can pass in anything and `node-docker-machine` wouldn't have...
https://github.com/blakeembrey/change-case/issues/65
Not implemented, a PR is welcome.
This is not a whole lot to go on. Is it `stderr` output, by chance?
What is the `CMD` and/or `ENTRYPOINT` of the image? Does that process exit?