Antoine du Hamel

I'm not sure what to do with this, I'm not happy with the solution I came up, and it doesn't look like any other solution make consensus so far. Also,...

> Checking in here again. I can say that all outstanding issues are complete and everyone who tries out corepack is very happy with it. Its solving real problems. For...

> I wouldn't consider signing releases a blocker to going stable. It would be a nice feature though. When discussing with other devs, I've heard a few concerns regarding the...

> (or use `$npm_execpath`, which practically noone does). TIL, that would indeed fix the issue! I suspect most `package.json` authors are not aware of this.

@developit Thanks for the answer, however it seems it doesn't apply to WASM files inside `node_modules` folder: ```sh rm -r your-project-name yarn create wmr your-project-name cd your-project-name mkdir node_modules/test curl...

> Is this after running npm install to ensure the file is there? Running `npm install` doesn't seem to help, the build fails anyway even though the WASM file is...

> would be good to drop yarn from the next major Node.js release series tags on Docker Hub, in order to provide leaner images. This reduces confusion, storage costs, and...

@xzyfer I tried to install the Emscripten SDK on my computer to compile libsass to WASM; good news, it compiles without changing the C++ code! I follow the following steps:...

Node.js team has added support for N-API on Node 6 and Node 8, what difference does that make for users to use N-API or `nan`? If the concern is about...

We should probably runtime deprecate it to move forward with this.