How to use with jiti to make it compatible with vscode-uri

[Miofly]

Describe the bug

0.4.9 run corret, but 0.5 more incorrect

Reproduction

no

Expected behavior

start error

System Info

System:
    OS: macOS Mojave 10.14.6
    CPU: (6) x64 Intel(R) Core(TM) i5-9500 CPU @ 3.00GHz
    Memory: 24.96 MB / 32.00 GB
    Shell: 3.2.57 - /bin/bash
  Binaries:
    Node: 16.0.0 - /usr/local/opt/nvm/versions/node/v16.0.0/bin/node
    Yarn: 1.22.10 - /usr/local/bin/yarn
    npm: 7.10.0 - /usr/local/opt/nvm/versions/node/v16.0.0/bin/npm
  Browsers:
    Chrome: 102.0.5005.115
    Firefox: 99.0.1
    Safari: 12.1.2

Additional context

No response

Validations

• Read the docs.
• Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.

[fi3ework]

@Miofly Could you give a re-production of how to use Vite & vite-plugin-checker & jiti together?

[fi3ework]

And thanks @Litarvan, this is properly a bug of jiti. If a re-production could be provided. I think it's easy to make a hack to compatible with jiti. Before 0.5.0, vite-plugin-checker only ships a CJS version. From 0.5.0, ESM and CJS version are both shipped and ESM is adopted by jiti IMO.

[Litarvan]

This is really strange, because it seems Nuxt is trying to load the ESM module in both a CJS and a ESM way. I've attached a reproduction of the bug itself in the Jiti issue.
It can also easily be reproduced by setting up a blank Nuxt 3 project, registering vite-plugin-checker, and starting the dev server.

In the meantime, I used a (dirty) workaround on my side which I've described in my own issue