As of this writing, I've only encountered it once in the wild. It was the multiformats package. It adds a brand new layer of complexity to resolving modules by defining an exports map that defines what consumers can actually import. Those imports aren't necessarily real file paths and may have layers of resolution rules of their own, depending on postinstall hooks or compilation variables.
Node documentation: https://nodejs.org/api/packages.html
Webpack documentation: https://webpack.js.org/guides/package-exports/
further.vim should support the standard.
Tooling is a little immature at the moment so I might delay the implementation until things settle.
As of this writing, I've only encountered it once in the wild. It was the multiformats package. It adds a brand new layer of complexity to resolving modules by defining an
exportsmap that defines what consumers can actually import. Those imports aren't necessarily real file paths and may have layers of resolution rules of their own, depending on postinstall hooks or compilation variables.Node documentation: https://nodejs.org/api/packages.html
Webpack documentation: https://webpack.js.org/guides/package-exports/
further.vim should support the standard.
Tooling is a little immature at the moment so I might delay the implementation until things settle.