-
-
Notifications
You must be signed in to change notification settings - Fork 3.5k
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
3.4.2 has breaking change math.div #1230
Comments
see #1228 |
lucy-vxt
added a commit
to lucy-vxt/electron-release-server
that referenced
this issue
May 12, 2022
Newer versions of bootstrap-sass-official are not compatible with the version of sass used in this project as it includes changes to the way division works. This issue is documented in these issues; twbs/bootstrap-sass#1231 and twbs/bootstrap-sass#1230. Making the version of bootstrap-sass required more specific stops the breaking upgrade.
ArekSredzki
pushed a commit
to ArekSredzki/electron-release-server
that referenced
this issue
May 12, 2022
Newer versions of bootstrap-sass-official are not compatible with the version of sass used in this project as it includes changes to the way division works. This issue is documented in these issues; twbs/bootstrap-sass#1231 and twbs/bootstrap-sass#1230. Making the version of bootstrap-sass required more specific stops the breaking upgrade.
thank you @lucy-vxt for ur suggestion it works with me |
emodric
added a commit
to netgen-layouts/layouts-ui
that referenced
this issue
Jul 6, 2022
thank you @lucy-vxt for ur suggestion it works with me too |
aminvakil
added a commit
to aminvakil/sportify
that referenced
this issue
Nov 11, 2022
aminvakil
added a commit
to aminvakil/sportify
that referenced
this issue
Nov 11, 2022
twbs/bootstrap-sass#1230 (cherry picked from commit 5474a44)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Upgrading from
3.4.1
to3.4.2
results in bunch of errors like below during build.Using:
node v16.13.2
npm 8.5.2
webpack 5.69.1
sass-loader 12.6.0
The text was updated successfully, but these errors were encountered: