-
Notifications
You must be signed in to change notification settings - Fork 21
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
Upgrade to bless ~4.0.0 #15
Comments
4 isn't out yet. Need to do this on a branch. |
We just pushed v4.0.0-alpha.0 to npm today! Please let us know how it works for you so we can be confident about getting the actual release out. Also, the Bless project has a new home at https://github.com/BlessCSS/bless. Since it is now in a github organization we'd also like to extend the invitation to transfer this repo there and add you as a member of the organization. The goal being to consolidate and document bless and it's usage with different build tools. Our main focus will be towards Gulp, Grunt, Webpack, and possibly Browserify. If you have any questions feel free to reach out in our issue log or hit us up on gitter at https://gitter.im/BlessCSS/bless |
It looks like bless v4.0.0 was released/pushed to npm today: BlessCSS/bless#89 Is it possible to update gulp-bless to use it? Thanks |
@BrandonNoad will take a look |
This might resolve BlessCSS/bless#92 |
Ok, I think it's ready. It would be good if you two could test #21 please; npm install adam-lynch/gulp-bless#bless4 |
When I try to build my css assets, I'm getting this when using adam-lynch/gulp-bless#bless4:
|
@BrandonNoad hmm :/. I'm not sure why that is. It looks like a problem with bless itself. @mtscout6 @paulyoung any ideas? Disclaimer: I'm completely guessing here. Bless (or a dependency) parses your CSS (AST) so maybe some invalid CSS could cause an issue. I know the stack trace shows the problem is in |
Ya, I noticed the error was in the bless module. I'm using gulp-sass to compile sass to css, and it's not throwing any errors, so I'm assuming the css is valid. Maybe the errors aren't being logged properly though...I'll have to double-check that. I'll do a bit of digging to see if I can find the root cause of the problem. |
If you can provide a simple CSS input that would cause this error it would really help us dig into what the problem is exactly. |
I've narrowed it down to 2 files in the foundation-sites (v5.5.3) library (the type and offcanvas components). I'll try to find the exact cause tomorrow. |
The following css rule when run through bless seems to cause the error:
|
OK I see there's a bless core issue. I'll close this and publish |
No description provided.
The text was updated successfully, but these errors were encountered: