Skip to content
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

Better extension handling? #68

Open
beckend opened this issue Mar 18, 2016 · 3 comments
Open

Better extension handling? #68

beckend opened this issue Mar 18, 2016 · 3 comments

Comments

@beckend
Copy link

beckend commented Mar 18, 2016

I have a loader which loads normal css(non local css) with extensions with accepts ".styl".
Then I have a loader which does the same but with local css ".l.styl"

I have tried extensions: [ '.l.styl', 'l.styl' ] but did not work correctly.

There is a ignore function property, but how about an include property for the plugin?

@mightyaleksey
Copy link
Member

I see, I need to check it first to tell you more. And I think it's possible to add include property.

btw, do you use any preprocessCss function?

@beckend
Copy link
Author

beckend commented Mar 21, 2016

Sorry for the delay, missed the question, yes I use your stylus preprocessCss in README.

@beckend
Copy link
Author

beckend commented Mar 21, 2016

Another example benefiting an include option would be this react component:
https://github.com/roylee0704/react-flexbox-grid
I would include only the correct regex to use local css, and the rest needs to be untouched, since they are supposed to load "normal" css files on the client side.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants