Kuno Woudt <[email protected]> writes: > The important thing IMO is to take this part of librejs and separate it > into an independent library, so it can be re-used by others to build a > command-line testing tool, or an online testing tool, or as a plugin for > some fancy IDE, or etc...
Yeah, thanks for clarifying this key point, Kuno. It would be useful to have the core LibreJS code refactored into a library that people could use however they wanted to. It won't be an easy task since the analysis code in LibreJS is designed so specifically to run with Mozilla's add-on API. I think a good approach on starting an independent library for LibreJS would be to use the LibreJS code not directly, but as inspiration. Off the top of my head it seems really complicated. One question that comes to mind: - Will this library need to have a headless browser component, to make HTTP requests to web pages and all their JavaScript dependencies? If so, would jsdom or PhantomJS work? I'll do some experimenting this weekend and see if I can find a path forward for this library. I'm thinking I should do this with node.js because it would be worth it to write this library primarily in JavaScript. Then it can be used by browser-based implementations of LibreJS.
