@rauchg Now add support for notFound(), forbidden() and unauthorized() in layout-less projects to return JSON errors. Ideally, having support for other HTTP errors or some kind of hook to handle errors such as _bad request_, would push nextjs as a first framework for API only projects.
@ctatedev@rauchg Monitoring dashboards. Being able to display multiple graphs (for user defined queries) would be tremendously helpful. Even if the page looks like the Usage page.
@leeerob I saw that recently you removed mentions of PPR from several Vercel projects. What’s the plan regarding it? Should we still consider it an experiment or could we bet it will ready eventually and start using it for projects that should hit production in the next 6 months?
@leeerob Hey 👋 I was looking at Vercel Commerce source code and found at that it uses Edge and revalidate. However, the documentation states that both parameters are incompatible. Which one is right? Next.js documentation or vercel/commerce? https://t.co/CaA0jpKWYi
@AlexBanzea Hey Alex. Would you mind considering adding a defense against the Hector Gambit in your Caro Kann course? The coverage in your course is amazing but somehow, this line is missing 😅
@leeerob hey! I’m thankful for all the work done by Vercel on 2022! Edge runtime is awesome to use! However the DX is not ideal. Is it possible to define a dev script in the package.json that runs them, without using nextjs? vercel dev ends up in an infinite loop…
1/8 My code style is getting simpler with every passing year.
Things I used to be into:
• Functional Programming (category theory etc)
• FRP (first and higher order)
• Domain specific languages
• Proper OOP (Smalltalk etc)
...
Today I barely use anything from the list.