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
I've been thinking about exposing the entire webpack config and allow users to overwrite it (similar to what Razzle is doing: https://razzlejs.org/docs/customization#extending-webpack), but I'm worried we'll regret that in the future. How would you see this being configured?
I'm not very skilled with custom npm packages and what the limitations are, but I was thinking one of two things:
1: caspar-graphics could check If a "webpack.config.prod.js" or "webpack.config.dev.js" file was present in either the src or root of the enduser project, and then use those instead of it's own /config folder.
2: The same as 1 but also add a tag to the build script. I.e. caspar-graphics build --customwebpack ./src/webpack.config.prod.js or something like that.
I'd like to be able to change fonts without recompiling the templates.
Is it possible to add something like this in config/webpack.config.prod.js in caspar-graphics via a parameter in the build script?:
The text was updated successfully, but these errors were encountered: