Gulp returns Error: no mixin named list-unstyled

Hello

Just set up a fresh sage installation (8.4.2) and get this error when running gulp.
If I remove the line with the mixin in _comments.scss, another one pops ups, and so on…

Any idea what the issue could be?

Thanks!
Aldo

assets/styles/components/_comments.scss
Error: no mixin named list-unstyled

       Backtrace:
       	assets/styles/components/_comments.scss:2
        on line 2 of assets/styles/components/_comments.scss
>>   @include list-unstyled;
   -----------^

Did you install the Bower deps?

Yes (bower install).
Strange is bower_components/bootstrap-sass remains empty.

All solved. Had to updated bower deps.

This didn’t solve the issue to me

This post isn’t helpful. What have you done so far to debug your issue?

You’re right, sorry for my poor post.

I’m using PHP Storm on Windows as development IDE. Everything (npm, bower, gulp, etc) work right. I made fresh installation of everything to the latest version (for node i installed the 4.4.1 LTS because it’s “Recommended For Most Users” instead of 5.9.1 Stable with “Latest Features”). I installed XAMPP 5.5.33 and i’m running locally “https://mydomain.com” (using the hosts file) (please note the “s” in “https”) that points to a WordPress last version with the last Sage last version (8.4.2) as theme.

It’s the first time i use Sage/PHPStorm/Gulp/Sass/Bower etc but i know what they do.

1st Problem: if i set “devUrl” in “assets/manifest.json” to “https://mydomain.com” browsersync ignores it and opens “localhost:3000” but if i set “proxy” to “https://mydomain.com” directly in “gulpfile.js” it correctly opens “https://mydomain.com:3000”.

2nd problem: if i modify “assets/styles/main.scss” in the terminal i get this error:

[10:26:17] Starting 'wiredep'...
[10:26:17] Finished 'wiredep' after 22 ms
[10:26:17] Starting 'styles'...
assets\styles\components\_comments.scss
Error: no mixin named list-unstyled

       Backtrace:
       	assets/styles/components/_comments.scss:2
        on line 2 of assets/styles/components/_comments.scss
>>   @include list-unstyled;
   -----------^

[10:26:17] Finished 'styles' after 35 ms

Thank you

Can you help me please? Thanks.

You still haven’t explained what you’ve tried to do so far to debug your issue

i didn’t try to debug that because i don’t know how to do. I’m providing feedback to report as best as possible the issue, so we can help each other to solve the problem and you can fix it in the next release. The only feedback i have is the error i quoted. If you set up a fresh installation you encounter that error and the build fails. Can i do something more to give you feedback? Thanks.

FWIW I just setup a fresh Sage install w/o errors.

git clone https://github.com/roots/sage.git cd sage npm install && bower install && gulp ... [14:33:22] Using gulpfile ~/sage/gulpfile.js [14:33:22] Starting 'clean'... [14:33:22] Finished 'clean' after 8.93 ms [14:33:22] Starting 'default'... [14:33:22] Starting 'build'... [14:33:22] Starting 'wiredep'... [14:33:23] Finished 'default' after 314 ms [14:33:23] Finished 'wiredep' after 393 ms [14:33:23] Starting 'styles'... [14:33:29] Finished 'styles' after 6.08 s [14:33:29] Starting 'jshint'... [14:33:29] Finished 'jshint' after 298 ms [14:33:29] Starting 'scripts'... [14:33:33] Finished 'scripts' after 4.17 s [14:33:33] Starting 'fonts'... [14:33:33] Starting 'images'... [14:33:33] gulp-imagemin: Minified 0 images [14:33:33] Finished 'images' after 34 ms [14:33:33] Finished 'fonts' after 84 ms [14:33:33] Finished 'build' after 11 s

1 Like

maybe the difference is that i didn’t clone the repository: instead, i downloaded the 8.4.2 release. Tomorrow i will try to clone and will give feedback (here is 12:00 am). Thanks.

Solved (both issues). Using the master branch everything will work. Probably the 8.4.2 release is broken. Please check and eventually fix it. Thanks.

Sage 8.4.2 is the master branch. As stated in the thread I linked several times:

Sage is tested on Travis CI with every commit to make sure that npm install, bower install, and gulp all work properly. Bugs can still pop up, but usually there’s something wrong with your environment if you can’t get things running.

There’s nothing to fix on our end. Looks like you fixed the issue on your end which is good.