Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Allow for wildcards in .scss

See original GitHub issue

mix.sass('src/style/*.scss', 'dist/style/');

As it stands, the above code results in:

This dependency was not found: * C:\.....\src\style\*.scss in multi ./src/index.tsx ./src/style/*.scss To install it, you can run: npm install --save C:\.....\src\style\*.scss

Example in:

src/style/main.scss
src/style/other.scss
src/style/another.scss

Example out:

dist/style/main.css
dist/style/other.css
dist/style/another.css

Issue Analytics

State:
Created 6 years ago
Reactions:4
Comments:23 (2 by maintainers)

Top GitHub Comments

30reactions

JeffreyWaycommented, Jul 11, 2017

We don’t support this at the moment. You should be explicit about each Sass file you want to compile.

Most projects just have a single app.scss entry point.

18reactions

divdaxcommented, Oct 3, 2017

@JeffreyWay I’m in the same situation like @Olian04

Currently i’m working on a project where we have 20 minimalistic onepager templates. Each template only needs his specific css and not a big merged app.css. This make sense?

We have our templates:

resources/views/templates/template1.scss
resources/views/templates/template2.scss
resources/views/templates/template3.scss
resources/views/templates/template4.scss
...

and have to update our webpack.js when we add a new template. It’s ok but a “wildcard” would be much nicer! 😄