From 45363ba83b662a16b54d0d8c92132062c33e83f7 Mon Sep 17 00:00:00 2001 From: Yoshua Wuyts Date: Mon, 23 May 2016 23:42:59 +0900 Subject: [PATCH] docs: add bulk-require --- README.md | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 73254c8..a424afc 100644 --- a/README.md +++ b/README.md @@ -481,14 +481,18 @@ we're using something even better. - [pull-stream](https://github.com/pull-stream/pull-stream) - minimal streams ### How can I optimize choo? -To bring down file size, consider running the following `browserify` -transforms: +`choo` really shines when coupled with `browserify` transforms. They can do +things like reduce file size, prune dependencies and clean up boilerplate code. +Consider running some of the following: - [unassertify](https://github.com/twada/unassertify) - remove `assert()` statements which reduces file size. Use as a `--global` transform - [varify](https://github.com/thlorenz/varify) - replace `const` with `var` statements. Use as a `--global` transform - [uglifyify](https://github.com/hughsk/uglifyify) - minify your code using UglifyJS2. Use as a `--global` transform +- [bulkify](https://www.npmjs.com/package/bulkify) - transform inline + [bulk-require](https://www.npmjs.com/package/bulk-require) calls into + statically resolvable require maps ## Hey, doesn't this look a lot like Elm? Yup, it's greatly inspired by the `elm` architecture. But contrary to `elm`,