Michaël Zasso
Michaël Zasso
What issue does it solve?
I don't know if it something that node-gyp wants, but from the Node.js perspective, it is unlikely to happen, as node needs to copy so we can build it offline...
> how could we keep gyp-next in the tree and avoid this from happening over and over again? The same question applies to all our bundled dependencies. I don't have...
`node-gyp integration` errors should be fixed in the node-gyp repo: ` not ok 2 - request to https://localhost:49373/ failed, reason: certificate has expired` Edit: I opened https://github.com/nodejs/node-gyp/issues/2645
> @targos https://github.com/nodejs/node/tree/master/tools/node_modules/eslint > > ESLint stays in `node_modules` and be added to repository tree. Maybe we can do it for gyp-next either? Maybe, but I don't see any advantage...
I won't object to this PR, but keep in mind that if we merge, someone's going to have to setup and maintain the npm release.
Windows CI is broken by: * nodejs/node#52682
For actions/setup-python errors, it seems to be: * actions/runner-images#9770
I'm not used to Python and have never worked with `typing`, so my opinion wouldn't be very informed. I work with TypeScript though and do like type annotations, so I'm...
As long as Node.js and node-gyp support Python 2 in their main development branches, I am against removing support here.