Synchronizing versions between the client package (+ debugger) and the extension (+ frontend) is a pain when one is downloaded from the npm registry and the other from a chrome web store. The packages get published at different times and there is no easy way to downgrade the chrome extension version to match the installed client version.
This is a trouble for me and for the users. Managing this in a repository of multiple people would be even worse...
So the debugger logic needs to be moved to the extension and injected onto the page with a content-script.
The client package will still be required, but the API surface that could change will decrease significantly - and that means less frequent breaking of changes even during rapid development - so synchronizing versions will be much easier.
Doing this should also eliminate this issue: #108 as solid-js version will be different.
solid-js loaded in content script would have to be in the prod version.
Synchronizing versions between the client package (+ debugger) and the extension (+ frontend) is a pain when one is downloaded from the npm registry and the other from a chrome web store. The packages get published at different times and there is no easy way to downgrade the chrome extension version to match the installed client version. This is a trouble for me and for the users. Managing this in a repository of multiple people would be even worse... So the debugger logic needs to be moved to the extension and injected onto the page with a content-script. The client package will still be required, but the API surface that could change will decrease significantly - and that means less frequent breaking of changes even during rapid development - so synchronizing versions will be much easier.
Doing this should also eliminate this issue: #108 as solid-js version will be different.
solid-js loaded in content script would have to be in the prod version.