feat: initial working vscode web extension

[jamesdabbs]

Partially addresses #5. There are a few cascading changes here that are related, but may not look like it:

• Getting the build system unified ran into an issue with vite v4
• Upgrading vite to v5 implied upgrades to vitest, sveltekit
• vitest had some breaking changes (snapshots, rejected promises)

[cloudflare-workers-and-pages]

Deploying topology with    Cloudflare Pages

Latest commit:	ee22e68
Status:	✅  Deploy successful!
Preview URL:	https://515b6bf8.topology.pages.dev
Branch Preview URL:	https://jcd-vscode.topology.pages.dev

View logs

[StevenClontz]

Offtopic: one day I should pick your brain on your pattern of using git push -f.

[StevenClontz]

I confirmed github.dev is using version 0.0.12. I'm getting this error when I click on a link:

[StevenClontz]

I believe the correct file path would be /pi-base/data/properties/P000188.md

[jamesdabbs]

Offtopic: one day I should pick your brain on your pattern of using git push -f.

I like a linear history that tells a story, so will try to git commit --amend liberally to make sure that PRs contain individual, atomic commits that could be independently applied. A lot of times this happens entirely on my machine and nobody notices, but if I'm concerned about external build stuff or integration testing, I push regularly along the way (hence a lot of --force pushing). I generally limit that to PRs that are in draft, and try to make additive changes after I reasonably believe someone has reviewed the existing work.

I confirmed github.dev is using version 0.0.12. I'm getting this error when I click on a link:

Just to confirm, you're looking at https://github.dev/pi-base/data and clicking on the link that shows up in the markdown hover preview, right? (Or – if you cmd+click on the actual ID itself or use VSCode's "go to definition", are those working as expected for you?)

I believe the correct file path would be /pi-base/data/properties/P000188.md

I think it's actually some arcane vscode-vfs://github%2B<hex/pi-base/data/..., but I see what you're saying.

[jamesdabbs]

... additive changes ...

like 113e67d

[StevenClontz]

Well, the link isn't broken, but now it's not even there. 🙃

[jamesdabbs]

Yeah, working on debugging it now. I have no idea why it would just silently not show up in the web, but work fine locally. It may take be a bit to get set up with some kind of process for remote debugging; I'm going to move this back to draft for now.

[jamesdabbs]

@StevenClontz – alright 53b3c7c should fix the links in hover text. The published extension seems to be working for me on github.dev but failing to activate entirely in a dedicated codespace. 🫠 Is that also what you're seeing?

[StevenClontz]

github.dev

Missing link at the bottom. Of course clicking the link at the top does nothing anyway - that's the same file as the item itself. Probably no need to have links here (but no big deal if it's annoying to special case this).

Clicking compact here successfully opens the file: 🚀

[StevenClontz]

codespaces

For whatever reason it did not install in my browser automatically (CORS thing seems new too but I haven't looked into it):

one-click install:

Nothing at first:

Refresh helps:

Clicking $T_3$ here works:

[jamesdabbs]

This was (squashed) merged in via #160.