Skip to content
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

deprecation warning with dart-sass #55

Open
tim-lai opened this issue Jun 22, 2021 · 7 comments
Open

deprecation warning with dart-sass #55

tim-lai opened this issue Jun 22, 2021 · 7 comments

Comments

@tim-lai
Copy link

tim-lai commented Jun 22, 2021

Hello, I just switched from node-sass to (dart)sass, and now I see this warning in my Cypress tests:

  More info and automated migrator: https://sass-lang.com/d/slash-div

   ╷
98 │   .w-two-thirds-ns { width: (100% / 1.5); }
   │                              ^^^^^^^^^^
   ╵
    node_modules/tachyons-sass/scss/_widths.scss 98:30  @import
    node_modules/tachyons-sass/tachyons.scss 72:10      @import
    src/style/main.scss 3:13                            root stylesheet

DEPRECATION WARNING: Using / for division is deprecated and will be removed in Dart Sass 2.0.0.

Recommendation: math.div(100%, 3)

There's actually quite a few warnings of similar nature.

Context: Libsass/Node Sass is deprecated

@kedarvijaykulkarni
Copy link
Contributor

@tim-lai
I fix this issue in the PR but it keep long open so you can use alternative reference to the following repository by installing as
yarn add --dev kedarvijaykulkarni/tachyons-sass#fix/deprecation-warning-with-dart-sass

@kedarvijaykulkarni
Copy link
Contributor

@tim-lai my PR is get merged you can take latest now

@fabianmarcus
Copy link

The Github Repo is fixed, but it seems that the npm module still has not been updated, isn't it? Could someone do so?

@RouL
Copy link

RouL commented Sep 20, 2022

@johno Please make a new release :)

@RouL
Copy link

RouL commented Nov 23, 2022

Seems like the project is dead :/
I hope Swagger considers changing to a different framework.

@l3ender
Copy link

l3ender commented Dec 5, 2022

A new version would be great--thanks!

@ledenis
Copy link

ledenis commented Apr 14, 2023

@mrmrs This issue is fixed on main branch but not published to npm, could we publish it? Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants