Sagui for more complex projects #310
Comments
This sounds fairly similar to create-react-app’s I guess the central question is what specifically can’t be done without "exporting". Is this about having better transparency of the bundled configurations? I can imagine if we have |
I don't know create-react-app 😄 . In my POV question is not [only] what can't be done, but how difficult things start to become, since some functionality requires changes to sagui to be done. This is the main blocker. |
So the idea is to modify the There is some background to this, which is why I mention |
So Sagui is very useful for kickstarting projects but it starts becoming a hindrance in the long run, since one needs to understand how Sagui works behind the scenes and also understand all the deps (Karma, Webpack...) and sometimes it falls short. For bigger projects it is generally preferable to be close as possible to the "lower level" config. Having this in mind, two suggestions:
Export from Sagui
An
export
task that exports all sagui config. Once someone gets to the point sagui becomes impractical they runsagui export
and continue from there.Sagui as a config compiler
Here instead of seeing Sagui as a runtime generator of config, we see Sagui as a config compiler. Of course, it could have both moder. This means one runs
sagui generate
orsagui compile
or something like that before running regular commands. These commands, in turn, will use already generated config, becoming much faster. User changes could be done in a different file and merged by sagui, solving the problem of conflicts when one regenerates the config. Ex:Of course names and paths are just what came to my mind, not a real suggestion.
The text was updated successfully, but these errors were encountered: