Hey Max! I updated the webpack config to use webpack 4 rather than 3 (they added a lot of sane defaults in that I thought would be cool for us to take advantage of) and made the configuration just a bit more modular.
You can now specify type of build you want from the command line (development or production) and automatically apply base config, anything we put in the mode specific config and apply any presets that the command line specifies.
I also removed some of the old npm modules that we weren't really using (like react) and stopped using babel to load jsx, because it isn't really necessary.
Let me know if you like it. I also double checked and yarn start is still working like a charm. I have no idea how to do the test-pa11y thing but if start and webpack are still working, I can't imagine I broke it too much.
Hey Max! I updated the webpack config to use webpack 4 rather than 3 (they added a lot of sane defaults in that I thought would be cool for us to take advantage of) and made the configuration just a bit more modular.
You can now specify type of build you want from the command line (development or production) and automatically apply base config, anything we put in the mode specific config and apply any presets that the command line specifies.
I also removed some of the old npm modules that we weren't really using (like react) and stopped using babel to load jsx, because it isn't really necessary.
Let me know if you like it. I also double checked and
yarn startis still working like a charm. I have no idea how to do the test-pa11y thing but if start and webpack are still working, I can't imagine I broke it too much.