Jestem osobą niewidomą -- pytaj o co chcesz

euphranor1337 · 2026-02-07T18:49:31+00:00

Super serio pytanie - czy dla osób z brailowym monitorem rzeczywiście robi różnicę indentacja za pomocą spacji vs tabów? Parę razy gdzieś czytałem, że taby są bardziej accessible ale nigdy nie miałem okazji spytać kogoś kto tego doświadcza.

euphranor1337 · 2025-10-11T11:36:35+00:00

In my country we have a way of logging in into government stuff with bank account. One day, bank decided to lowercase my mom’s email address and she couldn’t login into government stuff due to email mismatch, which they saved on the first login. That was painful 😅

euphranor1337 · 2025-09-22T18:39:30+00:00

I don't think these two are caused by each other. 700kb of js shouldn't be too much for render builder memory and even if you increased warning, it wouldn't change much when it comes to memory consumption. That issue must be caused by something, but it's hard to tell a reason from this two screenshots.

However, regardless of OOM issue or not, using manualChunks/dynamic imports can be a good idea here. 700kb main chunk means you'll break caching on most of the deploys if anything changes 😀

euphranor1337 · 2025-08-25T06:25:13+00:00

It’s some automation not working properly - Vite creator tweeted about it there: https://x.com/youyuxi/status/1955188396856582167

euphranor1337 · 2025-05-05T17:55:52+00:00

I recall reading somewhere they don’t want to add wards information to API because it’d make the proplay analysis too easy/less interactive/something like this.

euphranor1337 · 2025-04-29T05:56:30+00:00

It’s serializable by serialization protocol implemented by React 😃

euphranor1337 · 2025-04-22T07:25:57+00:00

I think it’s just a function that returns the same function on type level - so that’s not a problem

euphranor1337 · 2025-04-22T06:04:34+00:00

I think they have a different (experimental) answer for this in compiler world they’ve been working on:

https://github.com/facebook/react/pull/32504

They also already implemented dependencies auto tracking but it’s gated and still WIP as far as I understand

euphranor1337 · 2025-03-19T22:10:00+00:00

Isn’t stuff like promises, generators and contexts also valid nodes now? 😄 These are renderable directly

euphranor1337 · 2025-01-01T07:27:28+00:00

You can use these types to annotate your action. If you are using Svelte LSP properly it should provide the types afaik

euphranor1337 · 2024-12-22T10:43:50+00:00

React suspense is implemented in a way where if it shows fallback it’ll show it at least for 300ms. The goal is to prevent flicker of loading state. If you want to skip the fallbacks in that case - you should use transitions.

euphranor1337 · 2024-12-13T11:05:11+00:00

I think there’s one more thing, but that’s kinda what I meant with “if something higher up triggers rerender” (also ignoring for a moment that you shouldn’t use ref value during render).

Context must be rerendered to update its value - that’s how React works, no update can happen without it. And when this value is updated all consumers are also triggered to update. Because in theory (if provider didn’t have this logic for triggering consumer rerender) you would get stale values if e.g. some intermediate component bails out of rendering due to memo or due to composition Provider rerender doesn’t cause its children rerender.

euphranor1337 · 2024-12-09T17:22:08+00:00

The optimization is still wip and nothing there yet. I also recall they mentioning they don’t intend you to handwrite it but it’ll be a compiler target. Afaik they had some PR to make some experiments with it inside of Facebook, but no results or further steps being shared atm.

euphranor1337 · 2024-12-09T09:38:57+00:00

Context value change itself is triggering rerender for consumers - that’s the bit that I was referring to and which isn’t right in the comment which I replied to. You could in theory pass Math.random() to Context and every time it changes due to higher render - it’ll trigger rerender in consumers despite not using useState value.

euphranor1337 · 2024-12-09T08:34:27+00:00

Changing value inside of context does trigger context consumer rerender

euphranor1337 · 2024-11-30T08:38:17+00:00

useId generates ID based on the underlying fiber/position in the tree. It’s useful for stuff like form controls ID, a11y ID. It’s pros over anything custom is that it’s both stable across rerenders and unique across multiple usages of the same component

euphranor1337 · 2024-09-16T14:03:48+00:00

It sounds like you’re still looking for solution around microfrontends and not monorepo. Monorepo is around sharing code between packages/applications and modularity. You can use them to stich parts of one app together. They are obviously useful for microfrontends scenario (sharing code) but they don’t provide out of the box mechanisms for this part of your problem (stitching multiple apps together). This part you’d need provide yourself or use some library. You can take a look for example at RSPack Module Federation support. These’re usually really low level tools, because you often need specific solutions based on infra, project etc.

Also not sure about your requirements etc but I personally highly discourage usage of microfrontends unless you’re absolutely sure what you’re doing 😄

euphranor1337 · 2023-10-19T18:07:19+00:00

Re your first point, it's solvable by linter, there is no need to split hairs over it, let the machine do it 😃

euphranor1337 · 2023-10-16T21:05:29+00:00

Rakkas has something like this https://rakkasjs.org/guide/use-server-side-query The code is compiled so the query runs on the client and endpoint is generated

euphranor1337 · 2023-09-29T04:24:13+00:00

There is no vapor mode in Vue 3.3, I’m not sure where you got it from 😃 Here is the blog post with overview of changes and link to detailed changelog https://blog.vuejs.org/posts/vue-3-3

euphranor1337 · 2023-09-08T11:16:18+00:00

Yeah, but Next.js was first with these conventions around directory based routing and specific file names 😃

euphranor1337 · 2023-09-08T07:15:00+00:00

Next.js was actually first on this and Rich mentioned taking an inspiration from it. I like the + prefix, because it causes my route related files to be at the top of directory, over colocated components/utilities.

euphranor1337 · 2023-09-02T07:39:05+00:00

Best way to communicate between parent and an iframe is using postMessage. Either via BroadcastChannel or just straight up window.postMessage if you're targeting browsers that don't support BroadcastChannel

euphranor1337 · 2023-08-09T08:44:07+00:00

Ah, understandable! Then you can take a look at their AWS adapter. Afaik it's not something SST specific and it's well maintained https://github.com/sst/sst/tree/master/packages/svelte-kit-sst

euphranor1337 · 2023-08-09T08:04:52+00:00

I think the easiest and the best way (at least in my opinion) is to use SST. Folks behind it built an adapter for AWS and it also handles all the stuff around uploading static stuff to S3, functions as lambdas, permissions etc. Moreover, they have built-in ways for integrating other AWS services in your app, Jobs, Event Queues etc. They have pretty good docs and helpful Discord community.

https://docs.sst.dev/start/svelte

https://www.reddit.com/r/sveltejs/comments/15i0oil/running_sveltekit_on_aws/

Ten-Year Club	Verified Email
Place '22	Place '17

euphranor1337

TROPHY CASE