-
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
Incompatibility with bootstrap > 4.1 #1351
Comments
more additional informationMy package config:
|
Thanks for the report. Honestly I would have expected Bootstrap to follow semver and don't break stuff within same compatible range... I will need to investigate this. Thanks. |
@FezVrasta Thanks for the fast response. Yes I had the same prediction that bootstrap has made some breaking changes in it :( If you need someone for testing or something like that, let me know :) |
With 4.2.1 still works The breaking change: Thanks to @fooey: |
I've got the same issue i can confirm that @fooey his fix works node_modules/bootstrap-material-design/scss/mixins/_forms.scss line 159 |
Still the same... |
I just published 4.1.2 that should fix this issue, please report the issue here if it still happens. |
After you made this change, it made it incompatible with 4.2.1. It's too late now, but maybe next time, use a higher release number (i.e. 4.2.0) instead? We had bmd version set to ^4.1.1 and bootstrap to 4.2.1, which made it suddenly not work. I'm not that sharp on node and the package syntax/functionality, but I think ^4.1.1 means "compatible with 4.1.1", right? Hope you understand what I mean. And also, thanks for maintaining <3 |
Honestly the whole situation is very confusing, Bootstrap introduced a breaking change into a minor/patch version, which is against SemVer... After that, we patched our code to make it compatible with Bootstrap again, and made that in a patch version as well since that's what Bootstrap did. If I wanted to follow SemVer I should have released a 5.0.0, but then people would have asked why to use Bootstrap 4 they needed |
Hi, in my environment there are still bootstrap ~4.2.1 and bmd 4.1.1 is working. Therefore i think this issue is not really fixed well :/ |
Knowing the error would be extremely helpful 🔮 |
Hello. |
Does it work if you downgrade bootstrap to 4.3.x or 4.2.x? And are you sure that bmd is on latest version? :) |
@AndyClausen In version 4.3.1 of the bootstrap I have this error:
In version 4.2.1 and 4.1.1: I did the tests with version 4.1.1. I believe it is the latest available for npm installation. |
This might be a long shot, but could you check if the version strings have |
Any solution??? with @4.1 doesn't work |
There is a solution if you read the comments. |
Test Case
Sorry but I can provide a codepen test case because it seemed to be an compatibility issue.
I am unable to compile my stack via webpack, so I don't have a example.
Summary
I made a simple npm upgrade of my packages.
After the update I got the following error while running my webpack configuration.
The essential line is this one
Mixin form-validation-state is missing argument $icon.*
Additional Information
After I have looking for changes I tried to rollback the version of bootstrap version from 4.3.1 back to 4.2.1. Now all is working well!
Is there an known issue?
The text was updated successfully, but these errors were encountered: