Native module artifacts removed as extraneous: "Cannot find module"

[CrabDude]

Created for tracking purposes as I learn more & debug.

Do you want to request a feature or report a bug?
Bug

What is the current behavior?

Under certain conditions, build artifacts for native modules are removed as extraneous. (Removing extraneous file, verboseFileRemoveExtraneous). This

If the current behavior is a bug, please provide the steps to reproduce.

Seems to occur when yarn.lock would be altered by running yarn against a pre-existing node_modules install (off the current yarn.lock). The key output is:

warning Integrity check: Lock files don't match

This consistently reproducible across many circumstances, but not yet in a minimum use case. It has been verified that it is not caused by the respective native module, but will occur with any native node_modules given the right triggering circumstances.

What is the expected behavior?

Native build artifacts should not be removed in a manner that breaks native dependencies.

Please mention your node.js, yarn and operating system version.

[email protected]
[email protected], 0.24 (aka master HEAD)
Docker ubuntu12.04

Related issues: #231 #1955 (comment)

[bestander]

Should be fixed by #3224 and released in 0.24