As it turns out this is a bug in Next.js production builds.
I thought Effect was supposed to prevent errors? Why is it breaking T3 Chat? 🙃
Sebastian Lorenz
6,456 posts
- Effect now has 5 users.off for ~40 hrs... what did i miss?
- Agents are definitely NOT workflows.We should not try to make AI agents into something more complex than they are. Technically speaking, an agent is a workflow. Many agents are crons, of which workflows are a superset. Because agents are workflows, we’ve seen a renaissance of workflow builders: Zapier, n8n, etc
- Here is proof that Effect is coming to a frontend near youSome interactive effect-atom examples for ye.
00:00 - You can eliminate dynamically keyed properties on an object via destructuring with a computed/expression property key and the rest operator.
- Replying to @MichaelArnaldiThat's what triggered it yeah but each one by itself is an issue :-D
- Replying to @feedthejim and @dillon_mulroyThe bug can be reproduced with this branch on @jullerino's repro: github.com/juliusmarminge… And it can be resolved by disabling those generated alias rewrites highlighted in the link above.
- Proof of concept for preloading routes (react-router) in #React before transitioning using react-tree-walker. github.com/fubhy/react-pr…. Feels like a quick and elegant solution so far. Thoughts? /cc @mjackson @ryanflorence
- Just in case you haven't been following: Giulio has been working tirelessly on Effect Schema v4 for months and the outcome is absolutely incredible. This is a good starting point if you are curious:After a couple of months working on the new version of Schema (v4), I'm planning to gradually share a preview of some upcoming features over the next few weeks. Some are more mature and will likely make it into the final release, while others are still highly experimental.
- Do you use zod with typescript? Then you must definitely check out @EffectTS_ schema 🔄 Decode and encode 🔗 Equivalence ✌️ Discriminated unions 🪄 Classes 🛠️ Compose 🔝 Documentation
