-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Configs (postcss.config.js
)
#1147
Comments
Any news on this? The repetivtive calls to |
Just realised this issue is on postcss - I personally think the repetitive call memorization should live on postcss-loader - it's an issue with that loader in particular and not really to do with how you call postcss? |
The best place to solve it is Sorry, moving config to the core will not fix the problem. Anyway we will use the same library. |
Yeah it would make more sense to sit on Not sure I fully agree with the "memorize config for a minute or so" it's really only needed to "cache" / require the config once and then just pass that onto |
It could be too tricky in some systems. Caching for small period of the time could be more stable. But you should ask postcss-loader author. |
Tracking issue for including
postcss-load-config
(postcss.config.js
) into core directlyKnown 'Issues'
Perf
{Function}
callspostcss.config.js
,postcssrc.js
&&pkg.postcss
)Features
plugins
(e.g viaimport-cwd
|import-from
|resolve-cwd
|resolve-from
) (PostCSS CLI)plugins: <Array<Function(require)>>
won't workRefactor
{Error}
messagesfile
infoThe text was updated successfully, but these errors were encountered: