sean-roberts / browserextn Goto Github PK

Given the workflow and what is required from the developers side, what are the steps that the code will perform to publish an extension build?

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

Define the JS framework strategy for developers to consume. Obviously we have to handle consolidating the multiple apis from browser venders, how can we make that consolidation easy to use and accommodate the limitations of what some browsers may or may not support that others.

I would love to be able to bring the ability to insert build steps into the process. For example, if you wanted to compile less instead of doing it before running build with us, tell us that you want to do that and we can run that code.

Browsers will all have specific implementations for functions. We should have a very solid way of extending our framework for any type of browser/vender. And even better, maybe adapt a similar way to extend the framework itself for whatever the developer needs.