[Bug]: Extension doesn't work when nuxt project is in a sub folder of the workspace

[MartinTruRating]

Environment

Nuxt project info:

---

• Operating System: Windows_NT
• Node Version: v20.5.1
• Nuxt Version: 3.7.0
• CLI Version: 3.7.2
• Nitro Version: 2.6.2
• Package Manager: yarn@4.0.0-rc.43
• Builder: -
• User Config: app, devServer, devtools, telemetry, typescript, sourcemap, runtimeConfig, modules, i18n, device, pinia, googleFonts, imports, css, build, vite
• Runtime Modules: @nuxtjs/i18n@8.0.0-rc.3, @nuxt/ui@2.8.1-28248232.e404912, @pinia/nuxt@0.4.11, @nuxtjs/device@3.1.0, @nuxtjs/google-fonts@3.0.2
• Build Modules: -

---

What went wrong?

I was trying to use nuxtr when my nuxt project lives within a subfolder within the workspace (ie /src). But it cannot find it (see below

Is there a config setting that allows it to set the root dir of nuxtr so it can then pick everything up and work?

I tried using the monorepo DirectoryName config setting set to /src which enabled the extension and worked for things like creating components/stores etc but didn't for installing deps because it was trying to use the workspace root which is correct for a monorepo setup.

How to reproduce it?

Install nuxt into a subfolder structure like this:

Nuxtr isn't available in the sidebar or command pallete

[adhamfarrag]

Hello @MartinTruRating,

To be clear, your issue now is not being able to install dependencies ?
Also, /src dir has your whole Nuxt logic ?

[0vn]

I encountered the same problem, when Workspace mode is enabled, Nuxtr recognizes the first item in the workspace by default, and when my project is not ranked first in the workspace, Nuxtr does not recognize the item I need, and currently I can only fix this problem when I move my project to the first place

[adhamfarrag]

@Administrator-M can you elaborate more about "my project is not ranked first in the workspace" ?

[MartinTruRating]

@adhamfarrag Hello, yeah so the /src has everything in it from .nuxt folder to node_modules folder etc. But because the vscode editor is opened at the parent level above /src it would try to install packages at that level (if I enabled workspace mode).

It's like we need a combination of the two in a setting where you can specifiy the rootDir or something for where nuxtr starts working from

[adhamfarrag]

@MartinTruRating have you tried using "nuxtr.monorepoMode.DirectoryName": "src" ?

[MartinTruRating]

@adhamfarrag I did, so that then worked (as in I could use it to create components etc), but the problem then was when I tried to install/update any dependencies, it tried doing it in the folder above the src folder (which in a monorepo setup would be fine as the modules get installed into the root) rather than within the /src folder.

I've added the following rough directory structure if this helps at all

$root
 - .vscode
 - other root files
 - src (where the main app lives)
 - - .nuxt
 - - components
 - - composables
 - - node_modules

[adhamfarrag]

Got it.. I will refactor monorepo features and release it as soon as I can.

[MartinTruRating]

Brilliant, thank you very much! Make sure you still keep the monorepo functionality/compatibility for those that want to use that feature as I've used it on different projects :)

[adarsh4d]

@adhamfarrag Thanks for your awesome work on this!

To add more info regarding the issue faced by @Administrator-M, when we create Multi-root Workspaces if the first folder has a different project, then all the features provided by Nuxtr are not available.

For example, if the multi-root workspace is like this, it works

However, this doesn't work

The reason for using this approach is both has different language/framework and have their own source control. They are just grouped using the multi-root workspace approach to avoid switching windows.

[RihanArfan]

Experiencing the same issue. Here's my project structure:

├───apps
│   ├───application1
│   └───application2
└───packages
    └───base

[XStarlink]

Experiencing the same issue. Here's my project structure:

├───apps
│   ├───application1
│   └───application2
└───packages
    └───base

I have the same structure, and I'd love to use Nuxtr with the file creation templates it offers, but in my monorepo it won't activate...

[philippedasilva-orizone]

I don't know if that will help anyone but to ease my life with this current limitation, I created an extension allowing me to pick the nuxt project I'm working on and activate the Nuxtr extension for it on the fly.

You can find it here for the time being: Nuxtr Monorepo Project Switcher

I may publish it but I'd rather have @adhamfarrag to either release a better monorepo support or simply add it to the core extension ;)