Support for "package.json browser" style file replacement/removal within modules? about import-maps

[chase-moskal]

hey @andyredhead,

i was just looking into the "browser" field spec, which appears to be a defacto community standard, supported by bundlers like browserify, webpack, jspm, etc, however it is not documented in the npm docs.

this "browser" field concern may be more in scope for import map tooling, such as the tool that i maintain called importly that generates import maps, rather than the spec.

i have a hunch we may be able to add support for this in importly — import maps allow us to remap individual files — however a potential snag comes up with the ignore rules, eg "./example.js": false, where i suspect we may need to deploy some kind of funky hack like referring to an empty dud module or something like that..

importly is due for an overhaul anyways, to implement the imports/exports package.json standard, so we may as well throw support for the browser field into the mix as well.. reach out if you'd like to collaborate on it 😎 👍

[andyredhead]

Hi @chase-moskal , thanks for your reply. I'll take a look at importly (and resolve.exports).