sean-roberts/BrowserExtn

Layout desired developer workflow

sean-roberts opened this issue · 1 comments

sean-roberts commented

What should the developer expect to do when they begin to make an extension with this tool

sean-roberts commented

The current design for how we expect developer workflow should go is the following:

  1. Developers maintain one codebase (HTML, JS (references only to our JS API), CSS)
    Special note this directory must contain a extension.json file in the root
    2.$: build [installTo='browserName' | install ] type of cli to build and install/update
  2. [optional] $: install [installTo='browserName'] cli to manually install/update after the build process

I believe this two step process is simple enough and contains all of the points needed. The only hard requirement is that they have a extension.json file that tells us about the extension itself.