-
-
Notifications
You must be signed in to change notification settings - Fork 26.8k
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
Setting up CSS Preprocessor with npm commands #404
Comments
We will likely revisit styling in a few months and see if we want to add support for something like that. |
Yeah, looks clean and good alternative for the moment. Though I think it is worth adding. Or this cmd can run with the |
Another alternative is you could reference the loaders explicitly in the import statement. For example, first install the loader/dependencies
Then declare the loaders explicitly: import 'style!css!postcss!sass!./App.scss'; There are a lot of issues with this approach though:
|
How about specifying the
|
Sassport can be used for this: https://github.com/davidkpiano/sassport |
I haven't tried Like many of the users, I miss I also miss hot reloading, but I totally understand why it's not included. RHL3 needs some finishing touches, to say the least. Anyway, I promise to try Just an idea, but it would be really cool if some day one could do something like
Or maybe load some functionality via preset/plugins like we do with babel
Then add to a list of plugins in
|
I would like to have support for stylus. Could you add the stylus-loader for |
We don’t support this feature. |
If you want to make changes, you are a power user, and this project may not be the right fit for you 😄 . That said you can always fork
and it will use them instead. Of course you’ll miss out on our updates unless you take care of merging upstream changes into your fork. |
I’ll close this issue because we currently have no intentions on making CSS preprocessors a part of CRA setup. If you want to use one, please do as you did before Webpack: write SCSS/Less/Stylus/whatever and compile them to CSS with a CLI command. Then import resulting CSS into the project. |
This is now explained in the Sass integration documentation. |
Thanks @gaearon! Meanwhile, I created a basic boilerplate for myself to choose between |
I loved the utility and enjoyed working with default configuration without needing to configure anything.
Though after getting used to LESS/SCSS, I want to use it in the project.
But PostCSS is also a great tool, so don't wanna remove from the workflow. Though working with only CSS files makes it difficult sometimes and to plug preprocessor, it would require to eject from default config.
Like ionic, it would be good to have features; e.g. in ionic running
ionic setup sass
will setup the project for SASS/SCSS related workflow and and files; similarly running similar will set it up for LESS or SASS/SCSSThis would keep default scripts and need not to eject.
The text was updated successfully, but these errors were encountered: