feat(tsx): fallback to jiti when missing tsconfig.json

[userquin]

Description

Check unocss/unocss#3814

Linked Issues

Check linked UnoCSS PR

Additional context

[johannschopplich]

This should be resolved with TSX v4.11.0, specifically commit privatenumber/tsx@b6bf39b.

Also, with the latest release, tsconfig lookup can be disabled (privatenumber/tsx@3f42ae3):

tsImport('./file.ts', {
    parentURL: import.meta.url,
    tsconfig: false
})

So for Nuxt context, we can disable tsconfig lookup manually, right? 🤔

const mod = await r.import(path, {
  parentURL: nuxt.options.rootDir,
  loaderOptions: {
    tsx: { tsconfig: false }
  },
})

[userquin]

Not easy, we should provide the option to the consumer on every lib using importx, I dont like this behavior.

About nuxt, how do you know in unocss config package you are executing pnpm nuxi prepare first time (.nuxt folder)?.

[johannschopplich]

@userquin I feel you. But with the latest changes in tsx, the import won't fail anymore if no tsconfig.json was explicitly set via the config. Thus, even without passing the option tsconfig: false down from importx to tsx, it won't throw an error anymore. (getTsconfig is now wrapped in try/catch.) So with tsx v4.11+, it will just work in a Nuxt context.

[userquin]

superseded by #4

thx @johannschopplich ❤️