You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For js-in-css projects, we don't want a css file for components. Would be nice to have a project setting to skip that, like we can already skip the tests.
The text was updated successfully, but these errors were encountered:
Good point! I'm wondering if the correct way to go about this would be to rename the "cssExtension" property to "css" and accept false as a value, in addition to css extension strings. Eg
On Fri, Oct 20, 2017 at 11:55 AM Ragnar Þór Valgeirsson < ***@***.***> wrote:
Good point! I'm wondering if the correct way to go about this would be
rename the "cssExtension" property to "css" and accept false as a value,
in addition to css extensions strings. Eg
interface OptionsT {
[otherOptions: string]: any,
css: false | string,
}
This way we support both and could pass correct overrides in the cli:
cra-generate Foo --css=false
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#24 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAHBlgsrOlJOM_eyJdeyb-Hpgbv9lasFks5suIo7gaJpZM4P_Xzo>
.
For js-in-css projects, we don't want a css file for components. Would be nice to have a project setting to skip that, like we can already skip the tests.
The text was updated successfully, but these errors were encountered: