rwb has two goals.
rwb. There's a single entry in
rwbis updated, you'll get the latest webpack config for free.
This is a lofty goal.
npmbecause there's no standard way to include assets like images, fonts, and CSS.
rwbyou can assume that loaders are configured for CSS and images.
rwb-authored component in your existing app, run
rwb validate ./path/to/webpack.config.jsto validate that your webpack config has all the loaders that
rwbassumes are there.
The great developer experience of
rwb is a trojan horse designed to increase adoption of this "standard".
npm install -g git+mkdir myappcd myappnpm initrwb initrwb serve
You can change the port by setting the RWB_PORT environment variable:
RWB_PORT=3001 rwb serve
This will create
dist/styles.css. These files are optimized and suitable for production, though if you have a large, complicated single-page app you'll want to roll your own multi-bundle setup (
rwb will solve this soon).
When you go to production you'll have your own webpack config.
rwb validate will ensure that your config will work with components created with
rwb validate ./path/to/webpack.config.js
rwb staticshould do an opinionated production build.