Packaging for Multiple Targets

Howdy! Would you be open to a pull request that changes your build tooling to output distributable packages for multiple targets?

As is, it’s problematic to include this module in a project targeted for the browser due to use of ES6+ features (arrow functions, spread,…). I think it’s not uncommon for build tooling targeting the browser to exclude ./node_modules/ from transpilation (Babel). Of course… the user could always adjust their build, but… Also, the module built here doesn’t support tree shaking to reduce bundle size.

[staltz]

I understand, but callbags is a project built to be fragmented. It’s a good thing, I’ve worked a lot on concentrated projects and they suffer from trying to be everything for everyone. Have you read https://staltz.com/open-source-without-maintainers.html ?

So let’s try this: (1) fork whenever you think something could be better, (2) inform the original repo about the fork (3) update https://github.com/callbag/callbag wiki to mention your published fork, (4) let the strongest fork survive.

I’ll also try to update the readme on -basics to mention other forks of basics. That helps against making people lost.

[staltz]

Have you considered forking? 😃