Tim Roßkamp

What about the transpiled code? I can imagine that this would create a significant amount of overhead code.

Nicely done! But there are still a few issues: In the package.json `"jsnext"` needs to be replaced by `"jsnext:main"`. Eslint isn't working anymore. Maybe implementing the [rollup-plugin-eslint](https://github.com/TrySound/rollup-plugin-eslint) plugin will fix...

I made a [pull request](https://github.com/bennypowers/siema/pull/1) so it's easier for you.

Don't you think thats this gets a bit confusing for the regular user? I've never seen a .nomodule.js bundle in any js libary before, since .min.js is the common naming...

I could not find any good resources about external modules in rollup. But [here](https://github.com/rollup/rollup/wiki/pkg.module) is an explanation from the rollup wiki on how to serve an es module version of...

I would suggest to at least run babel over it before copying it over to the dist folder.

> give me some hint how to make it more rollup-friendly for other users? In the `package.json` you can define extra fields for modern bundlers using the `module` and `jsnext:main`...

I'm having the same issue. Here is the log with `-v debug` ``` $ pymcuprog ping -t uart -d attiny1616 -u /dev/tty.usbserial-A50285BI -v debug Connecting to SerialUPDI pymcuprog.programmer - INFO...