The import path must include the extension when publishing ESM as otherwise the module loader doesn't know how to find the file.
Fixes errors like:
Relative import paths need explicit file extensions in EcmaScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an
extension to the import path.
The import path must include the extension when publishing ESM as otherwise the module loader doesn't know how to find the file.
Fixes errors like:
This is a weakness of JSDoc types.
Refs: https://github.com/multiformats/js-multiformats/issues/249