Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Version synchronisation #14

Closed
thetarnav opened this issue Jun 12, 2022 · 1 comment
Closed

Version synchronisation #14

thetarnav opened this issue Jun 12, 2022 · 1 comment
Labels
enhancement New feature or request priority Important issue to focus on currently

Comments

@thetarnav
Copy link
Owner

Since the Chrome Extension is managed completely separately from npm packages — this could very easily lead to version mismatches and bugs because of that.
There needs to be an automatic version checker the would display a warning in the console, asking to update the npm package/extension, depending on which has a lower version.
The extension and extension-adapter should be a noop in a mismatch.

@thetarnav thetarnav added the enhancement New feature or request label Jun 12, 2022
@thetarnav
Copy link
Owner Author

Implementing #45 might lesser the importance of this (although it will still be necessary)

@thetarnav thetarnav added the priority Important issue to focus on currently label Aug 21, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request priority Important issue to focus on currently
Projects
None yet
Development

No branches or pull requests

1 participant