KHi @_matcheck. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:
K----------------------
The knowledge sources confirm that Nuxt has recently introduced the ability for modules to specify dependencies using the moduleDependencies property in the module definition, and that installModule is now deprecated in favor of this approach. With moduleDependencies, you can declare other modules your module depends on, and Nuxt will ensure they are installed before your module runs. You can also specify version constraints and provide configuration overrides or defaults for those dependencies Module Definition – Nuxt Docs feat(kit,nuxt,schema): allow modules to specify dependencies.
However, the knowledge sources do not provide a specific reason why @nuxtjs/i18n would not be recognized as installed when specified in moduleDependencies, even though other modules work as expected. There is no explicit documentation or issue referenced that describes this exact problem or a workaround.
Possible causes, based on the available information, could include:
The knowledge sources confirm that Nuxt has recently introduced the ability for modules to specify dependencies using the moduleDependencies property in the module definition, and that installModule is now deprecated in favor of this approach. With moduleDependencies, you can declare other modules your module depends on, and Nuxt will ensure they are installed before your module runs. You can also specify version constraints and provide configuration overrides or defaults for those dependencies Module Definition – Nuxt Docs feat(kit,nuxt,schema): allow modules to specify dependencies.
However, the knowledge sources do not provide a specific reason why @nuxtjs/i18n would not be recognized as installed when specified in moduleDependencies, even though other modules work as expected. There is no explicit documentation or issue referenced that describes this exact problem or a workaround.
Possible causes, based on the available information, could include:
- The module name or version constraint in moduleDependencies may not match the actual installed package.
- There may be a timing or order issue, but the new system is designed to resolve dependencies before modules run.
- @nuxtjs/i18n may have unique initialization requirements or checks that are not compatible with the new moduleDependencies system, but this is not confirmed in the sources.
KIf you are certain that the module name and version are correct, and the issue persists only with @nuxtjs/i18n, it may be a bug or incompatibility with the current implementation of moduleDependencies. The knowledge sources do mention that moduleDependencies is a new feature and that installModule is deprecated due to its shortcomings, but do not provide troubleshooting steps for this specific scenario.
In summary:
I'm sorry, but the knowledge sources do not contain enough information to explain why @nuxtjs/i18n is not recognized as installed when using moduleDependencies, even though other modules work. This may require further investigation or reporting as a potential issue to the Nuxt team feat(kit,nuxt,schema): allow modules to specify dependencies.
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------
In summary:
I'm sorry, but the knowledge sources do not contain enough information to explain why @nuxtjs/i18n is not recognized as installed when using moduleDependencies, even though other modules work. This may require further investigation or reporting as a potential issue to the Nuxt team feat(kit,nuxt,schema): allow modules to specify dependencies.
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------
K@1300178283945529427 Kapa.ai is still learning and improving, please let me know how I did by reacting below.
