a

@mohammed90 can you try this? when i run caddyfile adapt, i get ``` { "apps": { filesystems: {filesystems: [{"name":"foo","files_system":{...}} //... ``` not sure if this is right still.

note for myself: notify these projects https://github.com/sagikazarmark/caddy-fs-s3 https://github.com/tecosaur/caddy-fs-git

> Nit, but should it be `file_systems`? (Since it's two words) https://caddyserver.com/docs/caddyfile/options#storage dont think it's a nit, i think you're right, you already use file_system elsewhere in the project. will...

> Thanks! Is there a reason we need two? Like, why not just use the new `memoryStorage` for testing too? i'm not sure. // testingMemoryStorage is an in-memory storage implementation...

i can try to look for some time to investigate. i am usually afraid of changing existing tests.

@ankon using actual tmpfs may be an issue because of portability, is why i did not opt for this. especially on windows hosts, i don't know how to create a...

`echo "/status" | claude -p` does not seem to work either. i'm trying to do what this person is doing https://github.com/anthropics/claude-code/issues/1407#issuecomment-2995805615 but like that's a really deranged workaround lol...

personally i just cbor encoded into a mapping and stored it. no reason to overengineer the storing of less than a kilobyte. it felt important to keep this extensible. for...

im getting this same problem i think with `react-instantsearch` package, latest ver im trying ``` import {Hits} from 'react-instantsearch'; Hits; ``` and getting ``` main.tsx:1:20 - error TS2307: Cannot find...

oh, maybe it was the templated literal that was messing with things then? It wasn't working for me. Let me try again and see what happens. thanks!