using SASS @use "sass:meta" causes "issues" in bit status

[utillity]

Describe the bug

I have a styles.scss file in the root of my angular bit-app, which contains this in line 1:

@use "sass:meta";

bit status generates the following issue:

     > my.scope/web-app ...  issues found                                                                                                                                                                                                                                                              
       missing packages or links from node_modules to the source  (run "bit install --add-missing-deps" to fix both issues):
          src/styles.scss -> sass:meta

If I run bit install --add-missing-deps as suggested, of course there is no package sass/meta:

GET https://node-registry.bit.cloud/sass%3Ameta: Not Found - 404
sass:meta is not in the npm registry, or you have no permission to fetch it.
No authorization header was set for the request.

Steps to Reproduce

1. add an ng-app in your bit workspace with SASS support
2. add this to your scss file: @use "sass:meta";
3. run bit status

Expected Behavior

This sass command should not cause an issue in bit status

Specifications

• Bit version: (run bit -v) 1.10.0
• Platform: Windows 11
• Env: (if component-specific, run bit env and paste its environment) bitdev.angular/angular-env@8.2.4

[GiladShoham]

Thanks, we will fix it

[utillity]

thank you! that's the most pragmatic and solution-oriented answer I got in a while 😄

I guess any @use sass:* should be ignored (I assume bit can safely ignore any @use within scss files)

[davidfirst]

@utillity , I'm unable to reproduce. See screenshot attached.

In general, this is implemented. It knows to recognize such built-in modules. You can see this test as a reference:
https://bit.cloud/teambit/styling/deps-detectors/detective-sass/~code/detective-sass.spec.ts#l83

[utillity]

Hi @davidfirst I think it has been fixed in the mean time. I just haven't pulled the new version yet. Tilli