Add browserify outputs to package

[hildjj]

use the browser field in package.json? WIll unpkg.com use that?

[hildjj]

I don't think this should block the release. We'll need to do a 1.0.1 once we figure it out, but releases are cheap.

[hildjj]

ok, I've confirmed that everything should work if we add browser, unpkg, and jsdelivr.

[hildjj]

Before:

npm notice package size:  60.1 kB
npm notice unpacked size: 305.5 kB

after:

npm notice package size:  94.6 kB
npm notice unpacked size: 463.0 kB

I think it's worth the extra size for the CDN convenience.

[hildjj]

This worked fine, but now we need to change the order of operations for release. You'll notice that https://unpkg.com/peggy@1.0.0-rc.1/browser/peggy.min.js still says rc.0 inside, as does the embedded VERSION string. So, we need to run a build after the version bump, but before checking in and tagging. If we were using lerna, we would just add a version script, I think, but unless we're going to move to a monorepo (e.g. to pull out the CLI), lerna is massive overkill. I'll probably just write a script and jam it in tools/.

[hildjj]

OK, I just did rc2 using the release script. I like how simple it is. I suggest you don't use the script unless you have 2FA enabled on npm, because that gives you one last chance to bail before you can't recover.