fixed typos
This commit is contained in:
parent
baa6586252
commit
7e307a97cc
|
@ -38,7 +38,7 @@ A production pipe-line should *NOT* be in your way while **developing**. You sho
|
||||||
|
|
||||||
### How
|
### How
|
||||||
|
|
||||||
[RiotJS](https://riot.js.org/) [client-size compiler](https://riot.js.org/online-compiler/) is blazing fast, it only adds about 10kb, and it can easily handle thousands of tags/actions in hundreds of milliseconds.
|
[RiotJS](https://riot.js.org/) [client-side compiler](https://riot.js.org/online-compiler/) is blazing fast, it only adds about 10kb, and it can easily handle thousands of tags/actions in hundreds of milliseconds.
|
||||||
|
|
||||||
## Getting Started
|
## Getting Started
|
||||||
|
|
||||||
|
@ -92,7 +92,7 @@ Of course we want our component to do more, so...
|
||||||
|
|
||||||
## Build for Production
|
## Build for Production
|
||||||
|
|
||||||
When you are ready to move to production you can run `npm build`. This will create a `dist` folder with all your optimized assets, web-components, vendor dependencies and remove the riot `runtime-compiler` to shave off another 100kb
|
When you are ready to move to production you can run `npm build`. This will create a `dist` folder with all your optimized assets, web-components, vendor dependencies and remove the riot `runtime-compiler` to shave off another 10kb
|
||||||
|
|
||||||
Check out the [gulpfile](gulpfile.js) for all the build options if you do not want to build everything. Every task is commented, and split-up so you can grep it easily.
|
Check out the [gulpfile](gulpfile.js) for all the build options if you do not want to build everything. Every task is commented, and split-up so you can grep it easily.
|
||||||
|
|
||||||
|
|
Loading…
Reference in New Issue