Browserify does not like to eat his own output. When creating a npm library that is browserified make sure to derequire/minify the output so it can be reused in other projects without mystical ‘Cannot find module X’ errors where X is some file you know nothing about.
Possible fixes found in the wild:
noParsefor bundle A in the bundle B operation; or
- Running the standalone bundle through
- Minifying the bundle
if you own a library: make sure to minify or
derequire the package,
if you use a library: make sure to
noParse the library.