Kickoff Builds

[ashleynolan]

Moving the build conversation out of the v9 conversation here.

[ashleynolan]

@mrmartineau Just to address the last comment - I will already be maintaining a set of gulp build tasks here. If we could create the webpack tasks in a similar way then we’d have two different setups being maintained.

With respect to the maintenance anyway, most of the build tasks should change less frequently than the rest of the project. It tends to only be when we want to move away from a technology that a major change is required.

[mrmartineau]

@ashleynolan the fozzie repo is still private btw. We could definitely create a installable setup, kind of like kickoff-scripts already does. Perhaps instead, we use a community effort like Neutrino to manage this sort of thing.

With Neutrino, you install presets, there are official and community packages; see a list of community packages here: https://neutrino.js.org/presets/community-presets.html

[ashleynolan]

@mrmartineau Should be open sourced this week, but it’s on NPM currently. Basically it lets you pull in a set of gulp tasks and use those. So the logical thing would be that we could do the same with the webpack tasks – create a kickoff-build-webpack module that is installed and then changing this out for a different set of tasks is very simple.

Not sure how Neutrino works, but open to any ideas on how we could modularise these tasks. The goal with the one we’re building at JE is for this exact reason – so projects working with React/Angular/no framework can all have separate build tasks that can be shared across projects while also being very customisable to those projects.