-
-
Notifications
You must be signed in to change notification settings - Fork 503
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix sass package consumption via @use
#1132
Conversation
Review or Edit in CodeSandboxOpen the branch in Web Editor • VS Code • Insiders |
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
This pull request is automatically built and testable in CodeSandbox. To see build info of the built libraries, click here or the icon next to each commit SHA. Latest deployment of this branch, based on commit 94f867b:
|
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #1132 +/- ##
=======================================
Coverage 82.08% 82.08%
=======================================
Files 212 212
Lines 11184 11184
Branches 1343 1343
=======================================
Hits 9180 9180
Misses 1378 1378
Partials 626 626 ☔ View full report in Codecov by Sentry. |
6ba462f
to
7ab88fd
Compare
since `@import` is deprecated (https://sass-lang.com/blog/import-is-deprecated/), `@use` should be used (https://sass-lang.com/documentation/at-rules/use/) in order to allow importing from a nodejs package via `@use` we must annotate the `exports` field appropriately, see https://sass-lang.com/documentation/at-rules/use/#node-js-package-importer
7ab88fd
to
94f867b
Compare
since
@import
is deprecated (https://sass-lang.com/blog/import-is-deprecated/),@use
should be used (https://sass-lang.com/documentation/at-rules/use/)in order to allow importing from a nodejs package via
@use
we must annotate theexports
field appropriately, see https://sass-lang.com/documentation/at-rules/use/#node-js-package-importer