Building Chrome Extensions in Wappler

We are about to embark on a basic Chrome Extension to interact with our Wappler project, which got me thinking.

The basics of a CE are fairly straight forward, and as a non-coder I was able to build a test CE using Google’s tutorial.

Then looking through all of the documentation and a boilerplate project in a git-repo the general makeup of a CE isn’t too dissimilar to a basic Wappler project - e.g. CE’s use html/css/js and json, including things like manifest.json and package.json and even node packages.

In my uneducated mind it doesn’t seem a stretch that Wappler could extend to be able to 'no/low-code) Chrome Extensions?

Here is the extension built with the boilerplate, so you can see the file structure:

And here is the boilerplate: