Jici
April 9, 2020, 3:21am
2
This is a known issue with some plugin while publishing it. You can search the forum about that. This happen when Bubble minified the plugin code. So you need to cheat that to publish an uminified version.
@bubble
Hey bubble team,
I have hit this issue now for the third time (And I still have on hold 2 other plugins because of this). It seems like the closure compiler (minification) running on the plugin editor when submitting a new version does not support some of the new javascript stuff like Array.prototype.map()
[image]
I don’t want to publish my plugins with un minified code (to keep source safe) and I don’t want to rewrite/refactor the code (a reinvestment of my time)
When can we expec…
@keith For the ‘$jscomp is not defined’ error due to minification, here is the fix:
Open plugin editor
In console, enter window.do_not_minify_plugin = true
Publish plugin again
Test published version
If your issue is different, please submit a bug report.
And a lot of other
1 Like
