bug: SCSS doesn't rebuild when path is outside stencil directory

[James-Wilkinson-git]

Prerequisites

• I have read the Contributing Guidelines.
• I agree to follow the Code of Conduct.
• I have searched for existing issues that already report this problem, without success.

Stencil Version

4.13

Current Behavior

When you make a change to an SCSS file that lives outside of the stencil directory the changes are not picked up and re-rendered. This is an issue when using stencil in a mono-repo environment with shared styles.

Expected Behavior

Watcher should listen for changes and recompile scss when the files provided are changed.

System Info

No response

Steps to Reproduce

Edit the scss and see it doesn't update from red to blue for example.
https://github.com/James-Wilkinson-git/stencil-bug

Code Reproduction URL

https://github.com/James-Wilkinson-git/stencil-bug

Additional Information

Relates too #2635

[christian-bromann]

@James-Wilkinson-git thanks for raising the issue.

I am not really able to reproduce this. I checked out the code, installed the dependencies and ran npm start. I am able to make changes to the .scss file, see:

Anything I am doing wrong here?

[James-Wilkinson-git]

I blew away node_modules and package-lock did a fresh npm install and still the same issue it doesn't run. Also using VSCode.

My co-worker on a mac also sees the same issue, what could be causing it?

[christian-bromann]

Can you provide a step by step explanation how this can be reproduced on your machine using the reproducible example?

[James-Wilkinson-git]

I did… fresh install the repo and I have the problem. But you did It and dont. So something has to be up with the watcher source code compiling on install maybe? Node versions? Windows versions? I don’t know how that stuff works to help troubleshoot better

[christian-bromann]

Windows versions?

Are you on Windows?

[James-Wilkinson-git]

npm 8.19.4
node 20.10.0
Windows 10 Enterprise x64

[christian-bromann]

Thanks for this information. We were able to validate this defect on Windows. We will ingest this into our backlog and will prioritize it accordingly.

[tfrijsewijk]

Oh that's great news!

[James-Wilkinson-git]

This may be related, I might need to use powershell instead of git-bash inside vscode to get it to work until windows fixes microsoft/WSL#4739

[christian-bromann]

I might need to use powershell

Can you confirm that the expected behavior works using Powershell?

[tfrijsewijk]

For me it doesn't matter which terminal I use (PowerShell, pwsh, git bash or Mac's Terminal). Nested sass files are not change-detected.