-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Need a roadmap #167
Comments
A roadmap would be great, in the meantime please update this project. I can see renovate bot is hard at work, but Rollup version 1.0.0 was released 2018-12-28 with breaking changes: https://github.com/rollup/rollup/blob/master/CHANGELOG.md#100 Seems rollup-plugin-closure-compiler is stuck on "rollup": "0.67.4"... cheers! |
@steph643 I think some of the dependencies, inc closure compiler itself, are updated automatically: https://github.com/ampproject/rollup-plugin-closure-compiler/commits/master 28th Feb 19 >> Update dependency google-closure-compiler to v20190215 |
Thanks, @David-Else, but I'm not sure how to use this. When I install |
Apologies for the delays, I've been heads down on other projects. I'll return to fixing and improving this plugin in the coming weeks. Items I have prioritized:
|
Update: Was able to merge latest closure compiler version pretty easily. Its on master and will do a release. |
It's been a long time since I updated this issue, but I filed #252 today, adding support for Rollup > 1.0 with code splitting for simple mode Closure Compilation. |
Would it be possible to have a roadmap for this great plugin?
Here is why I think having a roadmap would be nice:
I've been hit by painful bugs in the closure compiler. So I filled issues in the closure compiler project. I've been answered that those bugs were fixed long ago! So I checked this plugin and discovered that the latest release is almost 6 months old.
So here I am, wondering what to do: waiting for the next release? Using the closure compiler manually? Cloning the project? A roadmap would really help making a choice.
The text was updated successfully, but these errors were encountered: