browser-resolve
browser-resolve copied to clipboard
browserify
resolve function which support the browser field in package.json
Some modules are [published](https://unpkg.com/[email protected]/package.json) with no `main` field in `package.json` and no `/index.js`, instead using `exports` to define the entry point for the module. They sometimes specify an entry point...
Related: https://github.com/defunctzombie/node-browser-resolve/issues/83 Notes: - I tried to keep changes to a minimal - I reused [this check](https://github.com/defunctzombie/node-browser-resolve/blob/f6cc86d9548747cade99cda06c74102ed4d384da/index.js#L64-L66) to differentiate references to module/file. This does mean that there are a number...
In addition to paths, it would be nice to resolve module names: ``` json "browser": "foo" ``` Before npm used to dedupe packages, it was possible to reliably do something...
Was deep in the bowels of a large `webpack.config.js` file and came across a challenge that this package seems perfect for solving – with one kinda catch. That is: _nearly...
Metadata
Owner
Metadata
resolve function which support the browser field in package.json