"Hot pushes" in Plasmo extension
I've built a Plasmo extension with multiple React components that I plan to share privately inside my company as a zip bundle. The challenge is that I don't want to redistribute the zip file every time there's a new version, and would like the zip file to only bootstrap the extension and for everything else to be loaded from a server. Is there a recipe for doing this in Plasmo? Alternatively I've noticed there's a "private" option for publishing in the Chrome Web Store and I'm wondering if that might be the right solution.
1 Reply
If everyone in your company is under the same domain or that you have a private tester group, then CWS's private option should suffice
I will implement private extension feature soon for https://itero.plasmo.com/
But at the moment, all extension on itero are public-facing link. Tho since there's no index, it's... pretty much private/unlinked xD
Just shipped private extension on itero, only available to professional plan under a team account.