-
-
Notifications
You must be signed in to change notification settings - Fork 336
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
typescript 4.8 support #1198
Comments
Seeing this same issue, here is a (complete?) list of issues found:
|
Tested with |
tested with |
My ts version was 4.5.4 got error.
I've same issue with 4.5.4 (my package-lock.json) is with that version :( |
Unable to update my Typescript version because of this issue :/ |
I've just released out vue-i18n v9.3.0-beta.11 Thanks! |
@kazupon : that looks promising, thanks! With updated dependencies, I 'only' get a different error on src/App.vue:19:8 - error TS2339: Property '$t' does not exist on type '{ $: ComponentInternalInstance; $data: {}; $props: Partial<{}> & Omit<Readonly<ExtractPropTypes<{}>> & VNodeProps & AllowedComponentProps & ComponentCustomProps, never>; ... 10 more ...; $watch<T extends string | ((...args: any) => any)>(source: T, cb: T extends (...args: any) => infer R ? (args_0: R, args_1: R) => ...'.
19 {{ $t('hello') }}
~~
Found 1 error in src/App.vue:19 Is that to be expected? Maybe related to #1190? |
Reporting a bug?
With a simple vue 3 and vue-i18n (e.g. v9.2+) typescript (v4.8+) setup, hundreds of circular constraints and index errors are thrown when building (tsc -c)
This does not happen in <4.7.4.
As a workaround, it is possible to
"skipLibCheck": true
in tsconfig.json. (see https://github.com/vuejs/tsconfig/blob/main/tsconfig.json / vuejs/vue-cli#5688)Expected behavior
without skipping typescript lib checks, it is possible to use vue-i18n with typescript 4.8+
Reproduction
https://github.com/ameinhardt/tsI18n
System Info
Binaries: Node: 16.15.0 npm: 8.5.5 npmPackages: see package-lock.json in reproduction repo
Screenshot
No response
Additional context
No response
Validations
The text was updated successfully, but these errors were encountered: