-
Notifications
You must be signed in to change notification settings - Fork 90
Rewrite the build system #1509
Comments
/subscribe @mmmavis |
@Pomax - how do you want to manage this ticket moving forward? Should we keep it in the current milestone? Or, are we done with it for now (my understanding), and therefore we should take it out of the current milestone - either to close or to pick up again later? |
I'd say let's take it out of any milestone but keep it around as a tracking ticket. It's not longer a thing that feels tied to specific heartbeats, but still appropriate to work through when there's a lull in the workloads. |
I feel like we're hitting a point where we really need to address this. With l10n tasks added, the testing system is starting to break (and take forever to do so), and it's hard to debug where it's breaking due to the Rube Goldberg-esque build system. Thoughts @Pomax @hannahkane @alicoding? |
Let's discuss in Going Global and Local Impact kick-off meetings today. |
we spent an entire heartbeat cleaning up the build system, this tracking ticket is now obsolete. |
It's worth rewriting the codebase build system to use webpack, babel, postcss, plus their associated loaders and plugins, to cleanly do a lot of things that are currently (necessarily) not as clean as the most modern approaches allow for.
Tasks that are necessary "before" a rewrite is even possible:
jsx
files to more modular forms (single class per file withrequire()
s, stateless components as straight up JSX, etc)Tasks that need doing as part of the rewrite
Tasks that will be good to follow up with
<IconLinks>
, because it's not DRY enoughThe text was updated successfully, but these errors were encountered: