The only way to clear the cache, from my experience, is to run a link via https://t.co/iZZGVlGPzX give or take 69 times, whilst hard-refreshing your tweet page 🥴
@engineering pls make Card validator as reliable as @linkedin's Post Inspector tool: https://t.co/DSaNqn1NrR 🙏
@leeerob Better docs / examples on self hosting this approach would be great. The microfrontends example doesn't cover the N nextjs apps use case and requires a lot of boilerplate hardcoded values about route rewrites, hardcoded ports, etc
@rauchg@vercel@v0@nextjs Maybe more turbo specific but support for multitenant nextjs applications that have many diff modules. Can do with the microfrontends example but lots of config and boilerplate to maintain each module
Ideally next would allow modules to define their own package.json,eslint, etc
@rauchg@DannyRaede@vercel@v0@nextjs Additionally a way to profile builds to understand the slowness. Is it the attempted SSG? Any specific pages with slow network request? Is it my machine?
If any of the above, how to easily opt out
@2co_p@leeerob I notice you are fetching in your server action, how do you feel about the guidance that "Server Actions are designed for mutations that update server-side state; they are not recommended for data fetching." from https://t.co/y4hJUDgb66.
See also https://t.co/1Z4or4tRia