You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
No sure if this is a known issue or if it's just come up and I'm the first one to report it. My research on the error had me trying some seemingly disconnected strategies for resolving the issue and none of them worked.
This package has never had an issue in the year I've been working in this repo but this week the build failed and I can't seem to figure out a fix. Anybody else seeing this issue? If it's a one-off thing I might just call it an L and use a different library 🤷
The text was updated successfully, but these errors were encountered:
I'm seeing this issue since my last build.
I'm using Node 14 and js-datepicker 5.18.0 for concerned project.
Strange it stopped working while no update has been made (running from a container on Github Actions).
My current option is that node-sass has been updated and now reject given syntax.
Curious about resolution of this bug, while I'm trying things on my side.
I'm still considering replacing SCSS dependency with built CSS import, but seems less "engineered".
@Skaantc / @tommy3wood I would assume this is a result of #122. If you are using the deprecated node sass i think it is possible that it doesn't support Math.div(). Node sass receives only maintenance updates no more features. You can try to switch from node-sass to dart sass -> https://sass-lang.com/dart-sass if thats no option you could pin the version of the plugin for now to 5.18.0, the PR was part of 5.18.1.
It says it should be a quite easy migration:
"If you’re a user of Node Sass, migrating to Dart Sass is straightforward: just replace node-sass in your package.json file with sass. Both packages expose the same JavaScript API."
No sure if this is a known issue or if it's just come up and I'm the first one to report it. My research on the error had me trying some seemingly disconnected strategies for resolving the issue and none of them worked.
This package has never had an issue in the year I've been working in this repo but this week the build failed and I can't seem to figure out a fix. Anybody else seeing this issue? If it's a one-off thing I might just call it an L and use a different library 🤷
The text was updated successfully, but these errors were encountered: