Prevent gulp from generating invalid 'display: box' rules #130
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Thanks 👍 |
|
How soon will a new version containing this fix be tagged so I can easily install it with npm? |
|
Waiting for a release also |
jacobwindsor
added a commit
to bridgedb/bridgedbjs
that referenced
this pull request
Apr 5, 2017
React Selectize currently has issues with autoprefixer. These have been fixed [here](furqanZafar/react-selectize#130) but haven't been tagged for release yet
|
Just to bump... Also waiting for a release |
|
Bumpity bumpbump |
|
We have been working around this since January by patching up the offending file. This however is rather brittle and our team would love to get rid of the hack. Any ETA on the next release? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I was having the same issue that was mentioned in #121 and traced the problem to the same issue that was happening here stylus/nib#312. Adding the fix suggested in that bug allowed for generating css that will no longer throw an error when using webpack's postcss/autoprefixer.