What do you want to see in a Vale browser extension?

[jdkato]

With the recent release of Vale CLI v3.0, I'm now shifting my focus to bringing Vale (back¹) to the browser. My goal is to initially support Chrome, Firefox, Opera, and Edge.

The plan is to use native messaging to allow the CLI to communicate with browser extensions.

Below is a rough outline of how I see this working.

Installation

The installation process will consist of two parts:

1. Running vale host-install <browser> to install and configure the native messaging host.
2. Installing the extension from your browser.

Usage

The extension will use the new global configuration file to control how it lints text on the web.

---

Please feel free to share thoughts or ideas on how this should work. Notably, given the nature of Vale (e.g., no cloud configuration), it's not straightforward to map project-based configurations to the browser.

Footnotes

1. As mentioned in https://github.com/errata-ai/vale/discussions/608, Vale Server (a now-deprecated desktop app) used to have a Chrome extension. ↩

[hamirmahal]

It'd be fantastic if

1. linting could happen client-side for lower latency, as opposed to making a round trip to an external server, and
2. users are able to run the linter on any arbitrary text input field in a browser.

[jdkato]

Both of these are already the case.