Fix typescript error for localization string $t
#966
Assignees
Labels
Comments
NabbeunNabi
added
bug
1 task
1 task
gminetoma
added a commit
that referenced
this issue
Jan 17, 2025
related to [#966](#966) - Update Nuxt to the latest version - Add a declaration file containing a patch for the issue - Update Nuxt config `compatibilityDate` to `compatibilityDate: '2025-01-17'` The main issue was that Nuxt previously used the @vue/runtime-core namespace to augment the vue namespace. This caused conflicts with any package using vue. As of Nuxt v3.13.0, they now use the vue namespace directly, which is the recommended approach. However, some packages, such as @auth0/auth0-vue, still rely on @vue/runtime-core, leading to compatibility issues. Our solution involved creating a declaration file to patch this problem. references: https://nuxt.com/blog/v3-13#vue-typescript-changes https://nuxt.com/blog/v3-15
gminetoma
added a commit
that referenced
this issue
Jan 17, 2025
related to #966 - Update Nuxt to the latest version - Add a declaration file containing a patch for the issue - Update Nuxt config `compatibilityDate` to `compatibilityDate: '2025-01-17'` The main issue was that Nuxt previously used the @vue/runtime-core namespace to augment the vue namespace. This caused conflicts with any package using vue. As of Nuxt v3.13.0, they now use the vue namespace directly, which is the recommended approach. However, some packages, such as @auth0/auth0-vue, still rely on @vue/runtime-core, leading to compatibility issues. Our solution involved creating a declaration file to patch this problem. references: https://nuxt.com/blog/v3-13#vue-typescript-changes https://nuxt.com/blog/v3-15
gminetoma
added a commit
that referenced
this issue
Jan 27, 2025
related to #966 - Update Nuxt to the latest version - Add a declaration file containing a patch for the issue - Update Nuxt config `compatibilityDate` to `compatibilityDate: '2025-01-17'` The main issue was that Nuxt previously used the @vue/runtime-core namespace to augment the vue namespace. This caused conflicts with any package using vue. As of Nuxt v3.13.0, they now use the vue namespace directly, which is the recommended approach. However, some packages, such as @auth0/auth0-vue, still rely on @vue/runtime-core, leading to compatibility issues. Our solution involved creating a declaration file to patch this problem. references: https://nuxt.com/blog/v3-13#vue-typescript-changes https://nuxt.com/blog/v3-15
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Problem
Currently there is a typescript error displaying for files that contain
$tfor translatable strings. This was previously fixed but seems to have become a problem again. We want to fix this as we do not want anytypescripterrors within our codebase.Success
This problem is researched and fixed. There is clear understanding through comments and a well written PR as to why and how this happened so going forward we can make sure this problem doesn't happen again, or can be resolved quickly.
Requirements
Implementation notes
This problem started when we updated our dependency in this PR. It should be related to this package version upgrade.
#939
You can checkout into the commit before this PR (by looking at the commits in the main branch) and build
.nuxtto see that there are no errors and then checkout into the hash of the commit of the PR to see that the errors then show up.The text was updated successfully, but these errors were encountered: