tomasklingen.nl
Senior frontend dev - currently working @chordify
I think I understand useEffect. 🤯
16 posts
16 followers
80 following
Getting Started
comment in response to
post
It’s only a problem if wrap changes right? If there something like <Parent wrap>child comps</Parent> there will not be any child re-positioning in the tree?
comment in response to
post
Maybe nicer to read but it has the same issue.
comment in response to
post
Reposting blog articles from 2023?
comment in response to
post
But what does this say about npm? It looks from the outside like it’s admitting pnpm is superior. It’s the opposite of dogfooding.
comment in response to
post
every time you think "maybe I should add a layer of caching in the application", take that energy and make the database faster instead
comment in response to
post
However, for true libraries builds, isn’t the for the consumer to determine/control what the final build looks like?
Similar discussion: ViteLegacyPlugin doesn’t work in library mode github.com/vitejs/vite/...
comment in response to
post
That’s a crazy coincidence. Today I fixed a bug we had with 2 webpack builds (normal + compat/legacy). Because the chunk names didn’t use hashes, they were using the same filename, one overwriting the other. Also: possible stale cdn cache issues across releases if names don’t change.
comment in response to
post
Nevermind! TIL wasm supports threads. 🧵 github.com/WebAssembly/...
comment in response to
post
Really cool! Nice work. Am I right in assuming this only showcases the speed improvements that come from the native code, but it misses the concurrency perf improvements that cli tsc 7 will have?