patak

Would you create a minimal reproduction of what your use case so we better understand it. Maybe it would be easier to discuss with a PR to show how the...

Thanks for reporting back @Maxim-Mazurok. My take is that this is expected in a Windows/NTFS system.

These links are not meant to be followed in GitHub. They work fine in the deployed docs https://vitejs.dev/guide/why.html But I think we could change this. I'll ask to others to...

Hey @danielkellyio, interesting bug. I wasn't expecting to log the whole Event object. I'm thinking it may be a good idea to destructure what props you want instead as it...

Leaving a reference here for a related issue with resolve conditions from @cpojer https://github.com/vitejs/vite/issues/17531. For Vite 6, we're working on a new Environment API proposal https://deploy-preview-16471--vite-docs-main.netlify.app/guide/api-vite-environment.html. I would appreciate feedback...

I think doing the same that Mastodon does is the best here 👍🏼

And thanks for your help to keep exploring the diff approaches with us @Aslemammad!

Nice! Leaving a reference here about [Local Only](https://github.com/hometown-fork/hometown/wiki/Local-only-posting) for others. I think it is a worthy addition. About the design, I would prefer we have the local-only icon on the...

I'll check this one once we know how to handle the Types 👍🏼 Let's see what others think about these extensions in the team too.

Thanks for the detailed answer @neet! @danielroe I'm wondering what is the best here long term. Neet has a good point that may also apply to us. Implementing every fork...