Francis Nimick

Here's our sveltekit solution, using a proxy defined in the server hooks - kitql library's `handleProxies` function: ```ts const SENTRY_UPSTREAM_URL = `https://${SENTRY_HOST}/api/${SENTRY_PRODUCT_ID}/envelope/`; const proxies = handleProxies([ [ "/api/sentry-tunnel", { to:...

This is more than an annoyance - this breaks pretty much all usage of tailwindcss, which uses `:not([hidden])` selectors extensively. Example: ``` .space-y-2 > :not([hidden]) ~ :not([hidden]) { --tw-space-y-reverse: 0;...

@abdel-17 a solution for now is to use e.g. `&:not(:global([aria-expanded]))` which works

Based on the current documentation: https://svelte.dev/docs/svelte/typescript#Generic-$props - it appears that the module script is no longer necessary? Or at least, having the previously required module block is no longer mentioned...

@endigo9740 why not simply remove `h-full` from the classes generated in the initials case to match the image case? I can't think of a reason for them to be distinct...

Ah, I understand. I've also updated and can't test with old safari versions anymore, unfortunately.

I am fairly sure this still occurs in v3 as an unnecessary `h-full` is still present on the text variant: see https://github.com/skeletonlabs/skeleton/blob/next/packages/skeleton-svelte/src/lib/components/Avatar/Avatar.svelte#L25 - `fallbackBase` includes `h-full` Why not simply remove...

EDIT: cleaned up the return type signatures ``` export function renameKeys< T extends Record, M extends Record, >(input: T, map: M): { [Key in keyof T as Key extends keyof...

Hm, the types here aren't as nice as I'd like when there is a collision in renaming. As an example: ```ts test("name overrides", () => { const obj = {...

@vishalbalaji with store-based reactivity it appears to work fine with svelte 5 as is - can you add this to your peer deps so we don't have to use `--force`...