tracking dependencies

To be mindful of our project's dependencies, let's track some basic stats. Bots can look through the actual git history.

These numbers are absolute totals at each commit. (meaning, don't add numbers together between snapshots, each is the total)

At each commit, run:

rm -rf node_modules
npm i

---

initialize SvelteKit

npm init svelte@next # yes to TypeScript, plain CSS, and Prettier, no to eslint

https://github.com/ryanatkn/kitty/commit/df44ca381b92562c6bd4af345353a9e1aa8a6932

added 46 packages from 111 contributors and audited 47 packages in 2.406s

---

install Gro

npm i -D @feltcoop/gro@0.6.4

https://github.com/ryanatkn/kitty/commit/8720c75a23977c136fd6e356c38a9314eca268e7

+ 71 packages
+ 15 contributors

added 117 packages from 126 contributors and audited 124 packages in 3.429s

Hey that's neat, Gro only adds 15 contributors. Its esinstall dependency along with some Rollup plugins add a lot of unwanted weight.

Also, Gro has dependencies that re-use 6 existing packages internally, to SvelteKit's initial 1. (if you do the math, that's what those packages numbers mean)

Gro also has the stated goal of offering a SvelteKit alternative to Vite, but that's a ways off. And Vite currently hides all of its dependencies like Rollup, by bundling the dependencies up and shipping with near-zero dependencies to npm. (for more about Gro see here and here) So maybe there's more contributors than it appears. (I haven't checked if Vite/Rollup include them somehow)

---

update Gro

npm i -D @feltcoop/gro@0.13.0

https://github.com/ryanatkn/kitty/commit/9770d19e40dfb04b89d3624d4a1ee3ad400c61f8

+ 7 packages
+ 16 contributors

added 124 packages from 142 contributors and audited 131 packages in 5.085s

Lots of updates to Gro. Adds 7 packages and 16 contributors, almost all through types and Rollup plugins, so not bad. Also not bad considering the improvements to Gro between 0.6.4 and 0.13.0.

Review the linked commits and recorded npm outputs first. The issue names no file, test, or implementation entry point and does not define a concrete tracking artifact, so clarify the scope and acceptance criteria before starting. Done should be an agreed dependency-tracking result.