-
-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
tracking dependencies #1
Comments
replace svelte-preprocess with svelte-preprocess-esbuildnpm i -D svelte-preprocess-esbuild@2.0.0
npm uninstall svelte-preprocess - 6 packages
- 5 contributors
Switching |
add Felt and upgrade SvelteKit and Gro dependenciesI wasn't keeping up with this so it conflates multiple changes, but the aggregate numbers barely changed: npm i -D @sveltejs/kit@1.0.0-next.120
npm i -D @sveltejs/adapter-static@1.0.0-next.13
npm uninstall @sveltejs/adapter-node # change to static adapter
npm uninstall vite # no longer needed with SvelteKit
npm i -D @feltcoop/felt@0.4.5
npm i -D @feltcoop/gro@0.34.2 - 3 packages
Sadly |
npm i -D @sveltejs/kit@1.0.0-next.131 - 6 packages
|
npm i @sveltejs/kit@1.0.0-next.179 + 2 packages
|
npm i @feltcoop/felt@0.12.0 + 1 packages
|
npm i @feltcoop/felt@0.12.0 + 48 packages 😢
This is a big sadface increase in Gro's dependencies, but adding |
npm i @feltcoop/felt@0.14.1 @feltcoop/gro@0.45.1 - 29 packages 🙂
Gro removed its frontend functionality in favor of supporting only SvelteKit, dropping |
npm i @feltcoop/felt@0.15.1 @feltcoop/gro@0.47.2 + 3 packages 😢
Some transitive deps changed in Gro, nothing major. |
npm i @feltcoop/gro@0.49.0 - 78 packages
Gro no longer has But at the same time, we install npm i -D svelte-check@2.3.0 + 54 packages
Bringing the total change to: - 24 packages |
npm i @sveltejs/adapter-static@1.0.0-next.26 + 3 packages
The static adapter added some glob utils. |
npm i @feltcoop/gro@0.50.3 + 11 packages
Gro added support for TypeScript type generation from schemas, adding the json-schema-to-typescript dependency. (I maintain a fork because I only use it programmatically, and Gro has its own things like formatting, so my fork is 11 deps vs 54 for the main project) |
npm i @feltcoop/gro@0.52.3 + 5 packages
Gro added support for args schema validation, adding the Ajv dependency. |
npm i -D eslint@8.11.0 \
@typescript-eslint/eslint-plugin@5.15.0 \
@typescript-eslint/parser@5.15.0 \
eslint-plugin-svelte3@3.4.1 \
@feltcoop/eslint-config@0.1.3 + 84 packages
Gro has optional support for eslint, and we've decided to integrate it by default in all of our projects. This adds eslint along with support for TypeScript and Svelte, and it uses our config @feltcoop/eslint-config. This is a big one, almost doubling our total dep count, but given the popularity of eslint in the community, adding these dependencies isn't as costly as it may appear, the benefits to code quality are substantial, and it's very nice to have it out of the box. |
npm i @sveltejs/kit@1.0.0-next.298 @sveltejs/adapter-static@1.0.0-next.29 + 2 packages
Big upgrade for SvelteKit. |
npm i @feltcoop/gro@0.55.1 - 1 package
removed a dep from Gro |
npm i @sveltejs/kit@1.0.0-next.340 @sveltejs/adapter-static@1.0.0-next.31 + 1 package
|
Upgraded esbuild via SvelteKit/Vite which added a couple platform-specific deps. + 2 packages
|
Upgraded SvelteKit from + 19 packages
|
Upgraded all the deps: + 0 packages
Hmm says 236 still? Maybe I missed an upgrade, doesn't matter. |
Upgraded to SvelteKit 1.0: + 1 packages
|
Upgraded to @sveltejs/kit@1.7.2: + 1 package
|
Some good churn in the eslint plugin and elsewhere: - 9 packages
|
Now included via SvelteKit: - 2 packages
|
Upgraded to Svelte 4 and changed from + 27 packages
|
- 1 package
|
gro changed to chokidar away from cheap-watch - ryanatkn/gro#386: - 1 package
|
gro had a major update with ryanatkn/gro#382 - 3 packages
|
- 4 packages
|
upgraded to - 4 packages
|
added + 2 packages
|
added + 1 package
|
removed - 2 packages
|
removed - 6 packages
|
added + 7 packages
|
upgrade @sveltejs/kit@2 + 1 package
|
upgrade @typescript-eslint/typescript-estree@6.16 + 1 package
|
upgrade deps - 7 packages
|
upgrade deps + 1 package
|
upgrade deps including Svelte 5 - 1 package
|
add + 1 package
|
Some deps were trimmed from - 6 packages
|
esbuild upgrade, nothing really added + 2 packages
|
upgraded to + 11 packages
|
Some more eslint-related churn - 7 packages
|
Big reduction mostly thanks to - 25 packages
|
ESLint churn +1 package
|
Chokidar dropped 12 deps but it's not yet updated in +2 packages
|
eslint netted out a dep -1 packages
|
Svelte 5 upgrade dropped a dep. -1 packages
|
Gro switched over to +3 packages
|
Eslint dropped -1 package
|
Svelte added +1 package
|
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:
initialize SvelteKit
npm init svelte@next # yes to TypeScript, plain CSS, and Prettier, no to eslint
df44ca3
install Gro
8720c75
Hey that's neat, Gro only adds 15 contributors. Its
esinstall
dependency along with some Rollup plugins add a lot of unwanted weight.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
9770d19
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.
The text was updated successfully, but these errors were encountered: