WTF is this?
This tool uses webpack and Rollup under the hood in order to bundle your project. The advantage here is that projext is way easier to configure and it does all it can to try and understand your project, so you don't have to write any configuration at all.
projext doesn't aim to replace webpack nor Rollup, it's just an easier way to use them for simple projects.
Besides abstracting the configurations, projext can also take care of "frameworks recipes", for example: for a React application, you know you need
@babel/preset-react and configure the hot loader on webpack... well, there's a plugin that uses projext API to do all that without you having to do anything.
Now, projext packages are organized in 4 different layers:
Configurations/Core: This is the projext package, the one that defines your project's targets configurations for the build engines and Babel.
Build engines: These are the plugins that use the configurations for specific build engines, like
Frameworks: These are the recipes for specific build engines, like
projext-plugin-webpack-aureliafor Aurelia with webpack.
Plugins: Extra functionality, like
projex-plugin-runnerto run Node projects on production.