J. Degand

I think tabindex is a considered an attribute and not a property. Even if you manually trigger change detection with ChangeDetectorRef and call detect changes or mark for check inside...

Well, it is both an attribute and a property. When you reference the HTML template, it is considered an attribute. For the TypeScript code, it is considered a property. Check...

@timdeschryver There is a website called [firecrawl](https://www.firecrawl.dev/blog/How-to-Create-an-llms-txt-File-for-Any-Website) that provides an endpoint to get llms files. Potentially, you could setup a monthly API request to get a new file. Also, you...

I should mention that using the markdown itself in the llms-full.txt file shouldn't trip up the AI (having `app-code-example` inside the txt file versus backticks with ts).

I have no real preference and those were the libraries that first came to mind. I will experiment and report any concerns.

I think `tsd` could become a stop-gap solution. Its maintainer is overextended so `tsd` is likely going to see maintenance mode level of activity. Beyond bumps to TypeScript, I wouldn't...

Yes, Vitest can't verify TypeScript error messages without external tools. I think the only real drawback besides that could be a false confidence in its results. I think it will...

`createEffect` is expected to return an object or function, but if a primitive (like a Symbol) is returned, it fails silently or throws a cryptic error. I think adding a...

`store.nullableObject?.value()` is unlikely to be a viable solution. Optional chaining short-circuits access, which means the signal graph may not track nullableObject as a dependency—breaking reactivity. This is why wrapping the...

For dynamic ids, I would try to enforce typing with `as` . `const userSignal = store[id] as DeepSignal;` Using a helper function would be preferred for larger codebases and maintainability:...