-
-
Notifications
You must be signed in to change notification settings - Fork 194
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
Recompiling with modifyVars #303
Comments
Sorry, it is limitation, we want to remove |
Ah - good to know. I'm using ant design, and modifyVars is their recommendation, but I'm sure there'll be another way to do the same thing! Is the 'we' wanting to remove it the webpack loader, or less in general? |
it is less-loader feature |
Are we definitely talking about the same feature? 😅 It’s on the less docs under the ‘modify variables’ section. http://lesscss.org/usage/#less-options |
Oh, my mistake |
The scheme for solving your problem:
|
This is a bad change, next |
@hooper-hc you can still use options: {
lessOptions: {
modifyVars: {yourVar: 'xxx'}
}
} |
Expected Behavior / Situation
Use modify vars, like the following
When in watch mode, any changes to
theme.js
will not be picked up, and you have to restart the dev serverActual Behavior / Situation
Actual behaviour is the expected behaviour
Modification Proposal
If we allowed the user to specify a path to modifyVars,
We can then modify
getOptions.js
with the following,(*) Note: I'm fully sure if there's side effects to adding a dependency outside of watch mode. I'm a bit worried it might sneak this file into some bundled JS output in some cases (although it doesn't seem to actually do this for me)
The text was updated successfully, but these errors were encountered: