Doesn't work for cleave.js

[pastelsky]

Doesn't work for cleave.js

[quantizor]

Don't be rude.

…

On Sun, Sep 10, 2017 at 6:19 PM tunnckoCore ***@***.***> wrote: @pastelsky <https://github.com/pastelsky> probably because most users don't know how to use Rollup correctly and same as you go to Webpack for no reason. In cases/services such as this site, where you use it to just bundle deps, but not using it for developing the site... is too much. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#10 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAiy1uyosUctpnr10CF354fo0lRav3tsks5shG5kgaJpZM4PJkbn> .

[pastelsky]

This project currently uses rollup to bundle dependencies, which fails at times with some packages due to how it expects the modules are published.

I'm rewriting this to use webpack, and that should fix these issues (in a week). Meanwhile you could try building this package with rollup to get an error stack trace.

[quantizor]

This can be closed, works with the new site. Thanks!

[tunnckoCore]

@pastelsky probably because most users don't know how to use Rollup correctly and same as you go to Webpack for no reason. In cases/services such as this site, where you use it to just bundle deps, but not using it for developing the site... is too much.

hint: https://github.com/Rich-Harris/packd, can use it directly.
From soon it already has hosted version at https://bundle.run

[tunnckoCore]

I'm totally not, just saying.

[pastelsky]

@charlike using a generic rollup config might work for 75% of the npm packages, but you need to
work around a lot more to solve for the edge cases.

Closing this since the original issue is fixed.