I love seeing PRs that add an extra 16 dependencies to the Svelte compiler and make learn.svelte.dev load more slowly for everyone so that a single developer can keep running Node 0.4!
github.com/A11yance/axobj…
Ben McCann
262 posts
Ben McCann
@BenjaminMcCann
Investor (@c3ventures) and entrepreneur. SvelteKit maintainer.
Co-founded Connectifier - acquired by LinkedIn
- Replying to @BenjaminMcCannPublic Service Announcement that you should never install deep-equal into your project as it pulls in a whopping 50 dependencies! npmgraph.js.org/?q=deep-equal
- svelte-preprocess is now dependency free! It is used in nearly every Svelte project. We've gradually reduced it from 44 dependencies in 5.0.0 down to zero in the latest release for faster builds, protection against supply chain attacks, and elimination of deprecation warnings.
- Svelte 5 is getting so stable! Down to single digit number of issues left...
- Node.js now has the ability to directly run code with TypeScript types! github.com/nodejs/node/pu… Current limitations: - Experimentally flagged - No transformations (enums, namespace, etc...) - No .js extension for .ts files - No running TS in node_modules
- Svelte 5 now supports hot module reloading (HMR)!
- The SvelteKit Cloudflare adapter just had its most impactful release allowing local simulation of bindings in dev and preview for developing with features like Durable Objects, KV stores, and R2 buckets! Learn more in the docs:
- We released SvelteKit 2.3.0 this morning with a new reroute hook. It allows you to choose to render a different route for the incoming URL. It has many uses, but was contributed by @loris_sigrist from @inlangHQ in order to support default lang parameters for easier i18n!
- SvelteKit's adapter system lets you easily deploy anywhere. We've released adapter-node v5 with a number of new features like graceful shutdown, socket activation, and asset precompression by default. Thanks to @karimfromjordan for authoring most of this!
- We just started work on SvelteKit 2. We'll be reviewing the issues tagged as breaking changes to see if they should be included as part of the release. Let us know if there any open issues that need to be tagged as a breaking change and considered for inclusion!
- I'm happy to see a growing awareness that Node 0.4 support plagues us all and that folks are stepping up to rip the code out in response. We are all better off thanks to their efforts. npm never ran on Node 0.4 so it's pretty hard to use and represents only 0.0004% of users.Love to see it, awesome work
- SvelteKit has a new docs page regarding performance optimization: kit.svelte.dev/docs/performan… Svelte 5 and the new @sveltejs/enhanced-img package are resulting in big Lighthouse boosts for early adopters with more to come!
- SvelteKit and Svelte 5 are now published with provenance attestation to help ensure the published package matches the source! Packages like UAParser.js, Command-Option-Argument, and rc have been attacked in the past. This is a great effort to secure the open source supply chain!
- Remember when one usage of is-number caused 440GB/week of traffic to npm? Well the only reason people where using it was because the popular chokidar file watcher did indirectly. chokidar v4 just dropped it and others resulting in a savings of 2.5 TB/week of traffic to npm
lol, removing is-number from this package saves 440gb weekly github.com/micromatch/to-…
