Support Native ESM in order to work properly in `vitejs` and TypeScript

[achmadk]

Hello. I have issue with void-elements library inside vite-based web application project.

This library is used by html-parse-stringify. I got error like this.

Although this library has support ESM with jsnext:main, unfortunately this library doesn't support native ESM, which required for vite in order to work properly.

Moreover, I hope this library also have built-in support TypeScript definition because definition file from @types/void-elements needs improvement to be stricter.

[francesc79]

please @pugjs merge the PR

[emab]

Is there anything else we can do to get this merged? Would be great if we can get this one in.

[achmadk]

Is there anything else we can do to get this merged? Would be great if we can get this one in.

You can use this module as workaround.

[emab]

Is there anything else we can do to get this merged? Would be great if we can get this one in.

You can use this module as workaround.

For me this is being used by html-parse-stringify which in turn is a dependency of react-i18next - is there an easy way to use your version instead?

I was hoping I could use the overrides property like this:

{
  "overrides": {
    "react-i18next": {
      "html-parse-stringify": {
        "void-elements": "@achmadk/void-elements"
      }
    }
  }
}

Is that correct?

[achmadk]

I have the same issue as yours. Although void-elements is deep inside react-i18next, all modules will be processed as flattened 1-level tree by vite.

import { defineConfig } from 'vite'

export default defineConfig({
  // rest of your vite configuration 
  resolve: {
    alias: [
      // another aliases 
      {
        find: 'void-elements',
        replacement: '@achmadk/void-elements'
      }
    ]
  }
})

That config works for me.

[emab]

Nice thanks for that. Will give it a go 👍