Files found outside of my Nativescript application are being picked up by the sass compiler. It appears it's finding my base assets directory (outside of my Nativescript application and not something I want compiled), and trying to compile one of the files there by itself and errors due to having no variable definition. This stops the compilation of my Nativescript sass files.
To perhaps make things a little clearer, my folder structure looks like so:

I am executing tsn run ios --syncAllFiles within mobile, but the compiler grabs things from assets as seen above.
The files within the assets directory are not referenced anywhere in my Nativescript application. The only defined scss files here are as follows:

The error I receive still points towards my assets directory:
Found peer node-sass
Error: Undefined variable: "$color-link".
on line 4 of app/assets/sass/components/buttons.scss
>> color: $color-link;
---------^
SASS compiler failed with exit code 1
Which platform(s) does your issue occur on?
I have seen this happen on the IOS emulator, but issue is persistent across both emulated environments.
Please, provide the following version numbers that your issue occurs with:
- CLI: 4.2.2
- Cross-platform modules: 4.1.1
- Runtime(s): 4.1.1
- Plugin(s): N/A
Files found outside of my Nativescript application are being picked up by the sass compiler. It appears it's finding my base
assetsdirectory (outside of my Nativescript application and not something I want compiled), and trying to compile one of the files there by itself and errors due to having no variable definition. This stops the compilation of my Nativescript sass files.To perhaps make things a little clearer, my folder structure looks like so:
I am executing
tsn run ios --syncAllFileswithinmobile, but the compiler grabs things fromassetsas seen above.The files within the
assetsdirectory are not referenced anywhere in my Nativescript application. The only defined scss files here are as follows:The error I receive still points towards my
assetsdirectory:Which platform(s) does your issue occur on?
I have seen this happen on the IOS emulator, but issue is persistent across both emulated environments.
Please, provide the following version numbers that your issue occurs with: