Add version numbers next to key integrations that are often not up-to-date with the GitHub version

[hippietrail]

Issues

N/A

Description

Some integrations take some time to update to the new Harper version once it's published on GitHub.

This PR adds the current version numbers for the Firefox, JavaScript/npm, VS Code, and Rust (Cargo) integrations.

I'm not really satisfied with the size and placement of the version text and font. I'm not a webdev guy.

I feel that the current GitHub release version number should be somewhere too so we can see how far behind any integration is. But I'm not sure where it would fit. I know to do the code as the latest version number is available at https://writewithharper.com/latestversion it would be trivial to add using the same methods the PR already employs.

I tried to add the Chrome one, but couldn't find any JSON feed or API and CORS prevents scraping the HTML. Google AI told me Svelte can do some kind of microserver thingy to fetch, but that sounded like going too far.

The LSP-based ones don't have version lag. Obsidian uses our repo. Did I miss any?

Demo

How Has This Been Tested?

Manually

AI Disclosure

• I am a human and didn't use any AI.
• I used LLM features of my editor, but not an agent.
• I used an AI agent interactively.
• I am an agent or I got an agent to do the work autonomously.

I got Google to iterate on the code too, which is between an in-editor AI and an agent I think.

Checklist

• I have performed a self-review of my own code
• I have added tests to cover my changes
• I have considered splitting this into smaller pull requests.

[elijah-potter]

I love the idea! I just have a few tweaks before we can merge this.

[elijah-potter]

It would be nice to have a small bit of hover text (which you can simply do with the title attribute) that explains why we are showing a version number there.

Something like, "This version is slightly behind the core engine due to a delay".

[hippietrail]

Ah I was wondering about something like that, sounds like a way to handle it.
Do you think I should also add the current version? We don't already display it anywhere. I'm not sure where it would look the best either.

[elijah-potter]

I would love a brief doc-comment that explains what this function does. Also, is there a reason you don't simply return a memoized copy of the liveVersions object? If you do, we can reduce the number of exports from this module.

[hippietrail]

I would love a brief doc-comment that explains what this function does.

Will do.

Also, is there a reason you don't simply return a memoized copy of the liveVersions object? If you do, we can reduce the number of exports from this module.

I'm not sure I really understand.