perf(nuxt): avoid watching nested paths

[danielroe]

🔗 Linked issue

resolves #20596

❓ Type of change

• 📖 Documentation (updates to the documentation or readme)
• 🐞 Bug fix (a non-breaking change that fixes an issue)
• 👌 Enhancement (improving an existing functionality like performance)
• ✨ New feature (a non-breaking change that adds functionality)
• 🧹 Chore (updates to the build process or auxiliary tools and libraries)
• ⚠️ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description

This handles an edge case, specifically when cloning a layer with a demo project located within it (like https://github.com/Atinux/content-wind/tree/main/.demo). Currently this means we don't properly benefit from the granular watcher pattern and exclude node_modules, .git and .cache folders within the subfolder.

Before watching a subfolder, this PR first checks whether it is a layer and if so skips creating the additional watcher.

📝 Checklist

• I have linked an issue or discussion.
• I have updated the documentation accordingly.

[Barbapapazes]

Hello Daniel,

It has been several times that there are performance issues on Windows. Do you think that it could be possible to have an automatic test to report it in the CI or It's too chaotic to test it? (like the test for the bundle size)

[danielroe]

I would be very much up for any kind of performance testing if it can be done in a non-flaky way. 👍

[Barbapapazes]

I would be very much up for any kind of performance testing if it can be done in a non-flaky way. 👍

I tried to write some scripts but here my pain:

• I want multiple runs in order to be able to do an average so I need to cleanup .nuxt folder. These runs must be one after the other.
• I didn't find a satisfying solution to stop dev server a the good timing (using a spaw is far from ideal because of the complexity added )