Error parsing "nuxtI18n" component option in file
See original GitHub issueVersion
nuxt: 2.14.7 nuxt-i18n: 6.15.3
nuxt.config.js
{
buildModules: [
'@nuxt/typescript-build',
'@nuxtjs/vuetify',
['nuxt-i18n', {
lazy: true,
langDir: 'lang/',
defaultLocale: 'ru',
locales: [
{ code: 'ru', file: 'ru.ts' },
{ code: 'en', file: 'en.ts' }
]
}]
]
}
At the beginning of the assembly, it issues such warnings, and not on all pages.
Could this cause problems?
Issue Analytics
- State:
- Created 3 years ago
- Reactions:3
- Comments:20
Top Results From Across the Web
Error parsing "nuxtI18n" component option in file #933 - GitHub
My component. When I delete get bc() , warning disappears. Perhaps, component style is bad way... <template ...
Read more >Why nuxt-i18n module doesn't seem to be loaded? ( _vm.$t is ...
I removed node_modules and .nuxt folder, reissue a yarn install but I still have this error, _vm.$t is not a function . Where...
Read more >A simple multi-language site with Nuxt.js and nuxt-i18n
Setting the parameters inside our configuration options in the nuxt.config.js file or inside each of our pages. If we choose the first method...
Read more >I18n Module - Nuxt
Custom routes optimized for Nuxt 3 file based routing - by @kazupon in ... don't crash on missing route when parsing page component...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Still experiencing this issue. In my case, it happens if I use any external variable/import in the
nuxtI18n
component options. E.g. this works:while the code below triggers the error and does not let nuxtI18n apply the in-component options for the page.
I was not able to overcome this issue, it’s a huge blocker
Edit: This issue is nastier than I thought. I get the issue even if I try to specify some TS typings. E.g.:
Of course, no problem. We are writing an application and it is open source. We are currently transitioning to nuxt3 and therefore are now in the nuxt-bridge version. For example, https://github.com/devind-team/dcis/tree/main/client.