Did you try to deploy your #Nextjs app today to #Vercel and it just doesn't work? Builds seem to be queuing up? You are not alone, there is currently an outage under investigation!
Curious about the future of web architecture? Wondering how Decoupled Drupal and NextJS can transform your digital presence? Look no further! Our comprehensive article breaks it all down for you.
Discover:
✅ What Decoupled Drupal is and why it matters.
✅ How NextJS integrates seamlessly into this cutting-edge architecture.
✅ The remarkable benefits it brings to your business.
But that's not all! We're not just talking the talk; we're walking the walk. As a leading provider of Decoupled Drupal services, we have the expertise and experience to take your web presence to the next level. 💼
Ready to unlock the full potential of Decoupled #Drupal with NextJS? Read our article now and get in touch to explore how we can make it work for your business. 📈
Don't miss out on the future of web development. Take the first step towards a faster, more engaging, and dynamic digital presence! 🔗#DecoupledDrupal#NextJS
Today I Learned what an HTTP 307 does that's subtly different from other redirect responses and that a NextJS res.redirect() uses it by default.
The 307 redirects to the new URL with the same request method (in my case POST). I was redirecting a form submit to an OAuth authorisation URL. Switching to an HTTP 303 swaps the method to GET and has sorted things out.
There's something really nice about declaring the form / inputs (even hidden ones for data that shouldn't be exposed to users) in JSX and then handling post'd form data in the action (which I guess would be "Server Actions" in #NextJS).
A Next.js app requires dozens of config files — next.config.js, eslintrc.json, tsconfig.json, package.json, postcss.config.js, tailwind.config.js, and more.
w koncu wrzucę release mojego self-projektu rowerowo-podróżniczego :) ... i bede musiał zmienić UI. z #tailwind na coś znacznie lekkiego i łatwego w utrzymaniu.
My team at HashiCorp has a few senior web engineering roles open! This is the team that builds all of our public-facing sites such as hashicorp.com and developer.hashicorp.com. Our sites are built with #React, #TypeScript, and #nextjs.
I hate that I'm so easily defeated, and derailed by unimportant shit. I can't tell you how often I find myself stuck in "can't install the PWA". It doesn't matter, it's an optimization, I should just move on and get easier wins. But this is something I've solved in other frameworks, this should be easy, and the fact that it's not just fills me with dread. The kinds of error messages I'm seeing, about server/client doesn't bode well. I'm reminded that I'm deep in #reactJS territory again. #nextJS
Directing a user of an airport website to the browser console... And the worse part in my opinion is, the page actually loads and then immediately removes the content to just show this message. Is this the common approach to show errors in #NextJS ? #frontend is really broken nowadays :(
The project I get paid to work on takes > ten minutes to install, build, and test from a fresh repo. That's not hyperbole. It's just two #websites built with #typescript#nextJS#yarn#nixOS and #jest. There aren't even any #e2e functional #tests!
We've come full circle!