Viewing profile — developit

This sounds fun

my unhelpful take is that I like both

<3

Nit: 212kb, the rest is a YouTube embed that I seem to recall is loaded lazily.

We are working on a new renderer that started out life as a way of addressing the specific corner cases that can lead to this. It will be released in early 2021.

It already does this. Only for .cjs files and things in node_modules.

The tooling space isn't broad enough to allow for differentiation across the board, so we have a number of tools that are working to validate/popularize a subset of functionality o…

Oh I totally agree it's strange, haha. The cost tends to be magnified in Node land since everything is a million files.

You need to change the HTML to point to the tsx file too: There are ambient TS definitions for CSS Modules, it just had a bug in 1.0.0 - fix is merged and will be released shortly.…

We've only shipped a helper library for Preact, but the Prerendering is actually generic. Some folks are working on helpers for other frameworks. The "API" is just a function expor…

It's built-in, just change the file extension to `.tsx` or create a new file with that extension.

It's designed for rapid prototyping. You can just use npm or yarn and ignore this feature though, it's entirely optional. FWIW the surface area for security issues here is far smal…

Hmm - it's not actually specific to Preact, it's just built by the Preact team and we use Preact in the docs. We are missing a bunch of documentation that would have made this clea…

tbh I think a good chunk of that size is babel-parser, which we're looking into removing from the preact ESLint preset. Still quite a difference though.

There are a few cases where syntax compilation is split up cleanly, but when you dig into the internals of preset-env, transforms are rarely that isolated. That being said, "watch …

Most specs have a small number of authors (1-3) and a much wider group of people who have influenced the spec. This is as true for Import Maps and kv-storage as any other. FWIW I t…

Not a great example, since "independent" is the important bit there: browsers just shipped sqlite, and you can't have a spec that says "just ship sqlite".

It's more than memory use - it causes tree traversals to take longer, which means unbounded style recalculations (common) and side-effecting DOM changes take longer.

Preact and Hoodie/PouchDB. Frontend hosted on Netlify, backend on literally anywhere ($5 Dokku one-click installation on a DigitalOcean VM, Heroku, whatever). Hoodie/PouchDB gets y…

It's possible now! https://developers.google.com/web/fundamentals/app-install-b...

It has a dark mode with different colors. Let's not villify blue in general though :P

For slow writers but quick typists, an app is always going to win out over a physical journal. Also interested in an event call export + parse.

It's true, the example could be better. However - adding any form of data pruning to the example would immediately show the benefit. JSON parsing happens in the worker, and only a …

Agreed! There's an open issue to address this - the single letter names are silly, since they get uglified anyway.