Replies: 3 comments
-
I can confirm. Okay i thought the issue came with But how to solve that? its a huge blocker Noteworthy, if you put the yarn.lock from your layer into the node_modules/your_layer of the app, you receive the following error: Cannot resolve vue-i18n on yarn! please install it on 'node_modules' But in package.json of the layer:
|
Beta Was this translation helpful? Give feedback.
-
Node Module Installation So I cant give further information, I will see how I can get beta.4 working for production, while this issue on newest versions persist.
Following packages have changed
|
Beta Was this translation helpful? Give feedback.
-
Issue according this Problem #2491 |
Beta Was this translation helpful? Give feedback.
-
Issue Description
Package Name/Repository: Nuxt 3 with Layers
Nuxt i18n Version: "@nuxtjs/i18n": "v8.0.0-rc.4"
Issue Details
I am currently working with Nuxt 3 Layers for my project. When I extend Layers from local repositories, everything works perfect. However, when I try to extend Layers from a GitHub repository link, I encounter an issue with the Nuxt i18n package. The specific error message I'm getting is:
ERROR No lockfile found from /***/node_modules/base-app
It's important to note that I have the latest version of "@nuxtjs/i18n" (v8.0.0-rc.4) installed in all Layers.
Steps to Reproduce
To reproduce this issue, follow these steps:
Create a Nuxt 3 project as a base Layer.
Use Nuxt i18n in the base Layer.
Push the project to a GitHub repository.
Create a Nuxt 3 project which extends the base Layer from the GitHub repository link.
Install the dependencies.
The base-app layer is added as a dependency in package.json as follows:
"dependencies": { "base-app": "git+ssh://github_pat_***@github.com:***/base-app.git" }
Expected Behavior
I expected the project to run without errors when extending Layers from a GitHub repository while using the latest version of Nuxt i18n.
Actual Behavior
Instead, I encountered the "No lockfile found" error as described above.
Additional Notes
I'd like to highlight that the described issue appears to be introduced in the latest versions of the library. To provide some context, I experimented with an alpha version of the library, and I couldn't reproduce the issue. This suggests that there might be a regression or compatibility issue in the most recent releases of the library, specifically affecting projects using Nuxt 3 Layers in conjunction with Nuxt i18n.
cc/ @kazupon
I would appreciate any assistance or insights from the community or individuals experienced with Nuxt 3 Layers and Nuxt i18n.
Beta Was this translation helpful? Give feedback.
All reactions