-
-
Notifications
You must be signed in to change notification settings - Fork 4.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Type support for Node16 module resolution #19606
Comments
Needs this for @hpcc-js/wasm/graphviz |
Any updates on this? |
We now support export default defineNuxtConfig({
typescript: {
tsConfig: {
compilerOptions: {
moduleResolution: 'bundler'
}
}
}
}) This mode is meant to mirror the actual behaviour of tools like Nuxt, which means it's likely to become the new default in future. But for now we've included it in our test suite so we won't encounter regressions. I would also appreciate testing of it in real projects. It is likely to reveal dependencies in your project (for example, Nuxt modules) that also need to be updated for this TS module resolution mode. |
Thanks @danielroe, we're testing the |
Works like a charm, thank you I'm having problems with vuetify though, leaving a link here just in case someone stumbles upon this issue Related vuetify link: vuetifyjs/vuetify#15885 |
We've now landed internal support for |
Follow on from #18426.
In order to have full support for Node16 format are:
.js
extension for relative import/exports in declarations unjs/mkdist#134imports.d.ts
upstream in https://github.com/unjs/unimport (cc: @antfu)~/.nuxt/tsconfig.json
need to include a file extension and/index
path/index
pathstype: module
in starterpackage.json
or otherwise provide recommendations on importing in CJS contextFor testing:
The text was updated successfully, but these errors were encountered: