Next.js 12.2: Middleware, On-Demand ISR, and Edge API Routes / SSR

preview_player
Показать описание

Check out the blog post for more information and upgrade today:

#nextjs
Рекомендации по теме
Комментарии
Автор

will get it. Just don't get burnt out. Whenever you need a break, take one.

heyybyee
Автор

I love Next.js! Best framework out there! Congrats to the entire team on constant improvement !

radanjovic
Автор

I love nextjs. i love vercel generally. it's nice that you are responding to developers that are pushing the envelope... but you need to address the fact that this is really just very niche cutting edge stuff. I'm sure it's useful but hello world examples for something like edge rendering gives no one any clue when or where or why we would use this. some of these things are basically brand new and almost exclusively done by vercel. would be extremely beneficial to your audience to invest in putting together some real world application videos. not just "look at this new thing! you can put an api route on the edge! you can have dynamic route matching for middleware! oh and you know how the <img> tag has been a thing forever? well we strapped a bunch of other stuff on it for our <Image> tag! unfortunately that didn't work out well and people basically hated it, so we reverted some of these changes to make it usable. we call it <Image> classic." this bleeding-edge stuff is great (I think, i understand most of them), but they require the most amount of hand-holding, they are the most app-breaking, and they probably are among the least performance-improving until the rest of us devs catch up. so throw us a bone. I would love to know if my SaaS software would benefit from edge api routes, but I need to know how much, and I need to know how to do it.

llampwall
Автор

Thanks to the nextjs team and to other collaborators for the amazing new features of nextjs 12.2

ken
Автор

thx team for providing so much value to developers

jingli
Автор

Amazing features 🤩🤩🤩 specially image components

Mufaqar
Автор

Damn Lee you just staying getting bigger job titles 😭 thanks for all these videos I’m just getting into next js after using vanilla react for a while and it was weird at first but now I love it!

To use the new experimental image for the no layout prop and all that, do you have to set up any new configuration for that? Or does it work either way you wanna do it automatically? Thanks again Lee! Can’t wait for another video and more next.js updates! ✨✨✨

obey_giant
Автор

The font choice for code examples was a bit "questionable" 😂😂
Otherwise, great presentation as always Lee!

phucnguyen
Автор

Not sure if this is the same for anyone else but I tried out the new image component and it seemed to perform worse than the previous one on LCP. I'm fairly new to performance monitoring but my lighthouse scores went up when I switched back to the old one.

zacharyallen
Автор

Code examples should use monospace font 😬

acarl
Автор

let's say I have a prebuild script that puts together a json bundle of some static data, would Edge API Routes be able to import that json file and have it bundled in the state it was in after the prebuild script? This could make for a very nice search api, provided the actual algorithm is written from scratch and not using any node_modules.

Mitsunee_
Автор

Amazing features and structure I really love using nextjs middleware. I have a question, how can I verify a token inside my middleware ? Thanks in advance

mamadouiliassasall
Автор

is edge runtime(middlewares) only available on vercel edge or any deployment?

ashwinyadav
Автор

What does :path means in config object?

dontqsy
Автор

So does 12.2 include Layouts RFC changes? I'm a bit confused lol

thelaitas
Автор

I have an issue with edge runtime why do need to add 'nodejs' for ssr can we not use 'experimental-edge' or 'edge' ?

Alihussain-rkci
Автор

Hi can I use this to send logs to Azure Insights

claytonvanderhaar
Автор

Interesting features but... If there's no backward compatibility to next/image for supporting the objectLayout layout=fill etc etc it will be a pain to migrate. Currently developing a large e-commerce project and this will be a pain to change. Also hope that edge will fix the performance issues of getserversideprops, it's very slow.

alexkey
Автор

New functionality requires new and more in-depth examples, all of this has a very high value but when you don't know the true potential to be addressed it's like the impact on developers is smaller, maybe a more real use case example would be more interesting than that just a "Hello World", ok ok ok, it's not that hard to understand, but the initiative to launch new things is precisely to approach who is entering the framework, as well as who is already in it and make both understand what is going on in the mind of the devs next.js when building a specific functionality, otherwise everything is very good I will put it into practice today

tiagomaciel
Автор

any ETA on the implementation of the RFC?

gorkacesium