When "main" matches source and "browser" field set, bundle fails.

Using browserify 14.4.0. masOS Sierra.

Quite a weird repro. When running this command:

browserify module.js -o dist/module.js

And under this set of circumstances:

• The "main" field in package.json matches the source file ("module.js")
• The "browser" field is also set (with any value, but in our case "dist/module.js")

We get this error when bundling:

Error: module not found: "/<pathroot>/module/module.js" from file /<pathroot>/module/_fake.js

Changing the "main" field to something else allows browserify to succeed. Removing the "browser" field also works. Of course these aren’t options for distribution.

[goto-bus-stop]

It looks like browserify or browser-resolve replaces the path matching the main field (eg. /xls-populate/lib/XlsxPopulate.js) by the path in the browser field (browser/xlsx-populateXXX.js) in some situations. I imagine this is good behaviour for modules inside node_modules, but not for local files. https://github.com/browserify/browserify/pull/1834 reproduces the problem.

[goto-bus-stop]

@stevenvachon

Both of my files are CommonJS modules, but I still experience this error.

When you do browserify lib, your browser field maps lib to lib-es5. It has to exist before that can be used.

I’ll close this since it’s actually the correct behaviour.