How do I prevent Drupal raising a segmentation fault when using a Node.js theming workflow? Symptoms:
Some drush commands fail; Some Drupal pages are blank.
The failing drush commands report &quot;Segmentation fault: 11&quot;
The Apache log (e.g. php-error.log in MAMP) also shows the same error.
Background:
If you use a gulp or grunt workflow - to compile your theme's SASS etc. - you may run into a problem where drush commands throw a segmentation fault 11 as does Apache whilst serving Drupal pages as blanks (WSDs).
Probable cause
This is because files from your grunt or gulp workflow environment in  node_modules are erroneously being registered by Drupal itself as a bi-product of drush cache-clear all for example. There are dozens of these .js files and Drupal can't handle them ... it's possibly a PCRE regex that is the root cause as this is known elsewhere. Anyway ...
It doesn't always happen
It's not clear whether some modules (like Browser Sync for example) induce this error as a node.js style (i.e. gulp or grunt) workflow can work perfectly before failing in this way.
Here is the solution you're looking for. Much more elegant and less work:

"scripts": {
  "postinstall": "find node_modules/ -name '*.info' -type f -delete"
}


Just a slight alteration on @iamcarico's answer above.

note: you may need a .npmrc with just the following content:

unsafe-perm = true