Having $lib/component with just $component was a bit confusing,
especially since $lib is also used in Svelte components all over the
place. This move will hopefully make it less confusing for me.
* Updated `vite` from 7.1.6 to 7.3.1
* Updated `@sveltejs/vite-plugin-svelte` from 6.2.0 to 6.2.3
* Updated `@sveltejs/kit` from 2.42.2 to 2.49.4
* Updated `@sveltejs/adapter-static` from 3.0.9 to 3.0.10
* Updated `svelte` from 5.39.4 to 5.46.1
* Updated `svelte-check` from 4.3.1 to 4.3.5
* Updated `typescript` from 5.9.2 to 5.9.3
* Updated `sass` from 1.93.0 to 1.97.2
* Updated `jsdom` from 27.0.0 to 27.4.0
* Updated `cross-env` from 10.0.0 to 10.1.0
* Updated `@types/node` from 22.18.6 to 25.0.3
* Updated `@types/chrome` from 0.0.326 to 0.1.32
* Updated `vitest` and `@vitest/coverage-v8` from 3.2.4 to 4.0.16
* Updated `@fortawesome/fontawesome-free` from 6.7.2 to 7.1.0
Builds the extension for both sites and uploads them as artifacts. This
will make it possible to just release the project and then grab the
ready-to-be-deployed archive for publishing.
This change was made using Cursor. Just a small test run to check how
useful it is for my workflows.
* Updated `vite` from 6.3.5 to 7.1.2
* Updated `@sveltejs/kit` and `@sveltejs/vite-plugin-svelte`
These are updated together, since they're interconnected with Vite
* Updated `svelte` from 5.33.14 to 5.38.1
* Updated `@sveltejs/adapter-static` from 3.0.8 to 3.0.9
* Updated `vitest` and `@vitest/coverage-v8` from 3.2.0 to 3.2.4
* Updated `svelte-check` from 4.2.1 to 4.3.1
* Updated `typescript` from 5.8.3 to 5.9.2
* Updated `sass` from 1.89.1 to 1.90.0
* Updated `@types/node` from 22.15.29 to 22.17.2
* Updated `cheerio` from 1.0.0 to 1.1.2
* Updated `@sveltejs/kit` from 2.31.1 to 2.42.2
* Updated `vite` from 7.1.2 to 7.1.6
* Updated `@sveltejs/vite-plugin-svelte` from 6.1.2 to 6.2.0
* Updated `svelte` from 5.38.1 to 5.39.4
* Updated `sass` from 1.90.0 to 1.93.0
* Updated `@types/node` from 22.17.2 to 22.18.6
* Updated `jsdom` from 26.1.0 to 27.0.0
Sometimes Firefox decides to load different groups of content scripts
asynchronously, causing our trick with `requestAnimationFrame` to miss
everything. To prevent this, I decided to just attempt to autorun
everything on each definition using `setTimeout`.
I've also tried to use `queueMicrotask` to put autorun logic right
between different groups of modules, but this trick was only working on
Firefox and completely breaking on Chromium. I sure love browsers!
