This installed the toolkit and then compiled it in place, with a comment claiming the install hook "does not run".
The hook runs. The compiled output was being packed out of the package afterwards, because the toolkit had no explicit file list and npm falls back to .gitignore, which ignores the build directory. Fixed in the toolkit, so the workaround here can go.
Verified by building both images on a clean machine with the step removed: the toolkit arrives compiled, and a module builds against the result.
This installed the toolkit and then compiled it in place, with a comment claiming the install hook "does not run".
The hook runs. The compiled output was being packed out of the package afterwards, because the toolkit had no explicit file list and npm falls back to `.gitignore`, which ignores the build directory. Fixed in the toolkit, so the workaround here can go.
Verified by building both images on a clean machine with the step removed: the toolkit arrives compiled, and a module builds against the result.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
This installed the toolkit and then compiled it in place, with a comment claiming the install hook "does not run".
The hook runs. The compiled output was being packed out of the package afterwards, because the toolkit had no explicit file list and npm falls back to
.gitignore, which ignores the build directory. Fixed in the toolkit, so the workaround here can go.Verified by building both images on a clean machine with the step removed: the toolkit arrives compiled, and a module builds against the result.