and you wouldn't learn technology that will be replaced in the next 2 years when react reinvent itself again tbh I was excited about nextjs with pages dir but after they added app dir I understood that this is over engineered and over hyped tech which will most probably die under its own weight in a few years anyway
Thank you, I was stuck on this post for a few days now, because I didn't find in the documentation how to create a post receiving the request body from the "body".
im still waiting for it to come out of beta. were going to do a main site redesign and I'm going app directory and tailwind the moment its stable. My dislike of styled components grows by the day since I moved to tailwind for everything else a while ago
I can't remember any longer the amount of ways there are to use the params/searchparams arguements. Looks like Every version comes with a new approach. 💀
I feel like I am missing something. Where is the information saved? Where is the database? Is this all just saved on runtime or am I misunderstanding this?
yes, background, sorry. yeah, eg. the import pokemon from "../../pokemon", only display as mport pokemon from "../../pokemo, the i in the beginning and the n" at the end doesn’t show in the screen, this happens in others shorts vídeos too.
@@robertojnior Ah ok. I guess there is a smaller zone of safety for content then the regular 1080x1920. Sigh. 1080x1920 is already tough enough to show code in.
In term of best practice, suggesting that we are using an ORM like Prisma, you should use your query builders from prisma directly in this route.js files right?
It's really just the typings, you get more info about the request with NextRequest. But since I'm not using it in almost any case it really doesn't matter.
You only get a single function for each api route and you have to figure out for yourself the HTTP verb. It's not a big deal but DX improvements like this are nice.
Why the hell do you want to make an api with a Frontend framework? It's a subpar solution but people who haven't used real backend frameworks won't realize it.
I use what you taught me at daily work.
Awesome! I actually created a helper library when that was not possible, it's called 'next-rest-controller' and another called 'next-api-validation'
Would've been much easier to learn dotnet or django.
and you wouldn't learn technology that will be replaced in the next 2 years when react reinvent itself again
tbh I was excited about nextjs with pages dir but after they added app dir I understood that this is over engineered and over hyped tech which will most probably die under its own weight in a few years anyway
You make excellent content Jack! Thank you! Love your channel!
Thanks for the quick summary! Will you be posting a more detailed tutorial on how to build a REST API with Next?
Thank you, I was stuck on this post for a few days now, because I didn't find in the documentation how to create a post receiving the request body from the "body".
Every video without Pokemon is incomplete
im still waiting for it to come out of beta. were going to do a main site redesign and I'm going app directory and tailwind the moment its stable. My dislike of styled components grows by the day since I moved to tailwind for everything else a while ago
This is a lot cleaner. Makes nextjs more like a balanced backend framework. I believe that's their target.
Please 😮 make a detailed video on this
It Is interesting to see how this Framework changes all time
Just barely getting started with nextjs. Is there a reason why you didn’t create the Pokémon directory inside the api directory?
Hey I was wondering what theme you use? I am using webstorm and hope there already is your vscode theme done for that 😅.
Night Wolf [black]
I can't remember any longer the amount of ways there are to use the params/searchparams arguements. Looks like Every version comes with a new approach. 💀
I feel like I am missing something. Where is the information saved? Where is the database? Is this all just saved on runtime or am I misunderstanding this?
Awesome content!
Just one feedback, for some reason the video bg is being cut off in mobile.
bg? background? like cut off how?
yes, background, sorry. yeah, eg. the import pokemon from "../../pokemon", only display as mport pokemon from "../../pokemo, the i in the beginning and the n" at the end doesn’t show in the screen, this happens in others shorts vídeos too.
@@robertojnior Ah ok. I guess there is a smaller zone of safety for content then the regular 1080x1920. Sigh. 1080x1920 is already tough enough to show code in.
In term of best practice, suggesting that we are using an ORM like Prisma, you should use your query builders from prisma directly in this route.js files right?
Yes
wtf i've been learning to do this for the past 6 hours with basic node.js and babel😭
Which vscode theme and fonts are you using?
This will be a great tutorial for crud and image and file rest api creation
Hope you do it 🙏
Very interesting. Thank you so much. Could you please tell me what theme do you use in you editor?
Night Wolf [black]
@@jherr thank you so much for the answer.
Short and Simple. What font and theme do you use? Looks so good
JetBrains Mono and Night Wolf [black].
Great for simple stuff
but the bad side of this next js, cant get req.body, example we use form urlencode
My wife has been overhearing my RUclipss over the last year and thinks I’m into Pokémon
Sorry Mrs. Dunning. Maybe I''l do a video that uses something like Ted Lasso episodes. :)
@@jherr lol has to be The Office
@@ToddDunning That would be tough for me. I only watched a little of that show. (I know, I know.)
how to make one file somethingAPI.js that can handle get and post with query params or optional only in one file ?
is this only for the "experimental app folder" version? or works for any app in Next13?
Thanks
Yes, for the App Router only.
@@jherr thank you
which font and theme, do you use?
Theme is Night Wolf and font is Jetbrains Mono
Any specific reason to use Request instead of NextRequest ?
It's really just the typings, you get more info about the request with NextRequest. But since I'm not using it in almost any case it really doesn't matter.
hello, so i try to redirect POST function how can i do that
What's the name of your vs code font ? And theme
why params only work in second parameter, if use only params without request parameter, it doesn't works
Which theme is used in this video ?
Night Wolf
These are server side routes right?
hi sir, why request.json() not working in me? error code not run
why its not on API folder?
May i ask what font you use? Thank you! ❤
JETBrains Mono.
@@jherr thank you
Your vids are so crisp. Whats the secret sauce ?
Talking really fast. :)
Cowbell
I wonder how much easier it is compared to next 12?
In there you just create a file inside "API" directory and the file itself is an endpoint.
You only get a single function for each api route and you have to figure out for yourself the HTTP verb. It's not a big deal but DX improvements like this are nice.
Whats the color theme please?
Eski full vidio h kya
What vs code theme is that? 😍
This looks suspiciously like sveltekit :3
Good ideas have a way of getting around. :)
ow we access the get result in component?
whats the vs code theme and font please?? 🙏
What colour theme is that?
Awesome video😮.
Which font is this ?
I like the font. What is it?
Jetbrains Mono
What about search params?
Cool, im gonna use nexths to build all my apis😂.
i think their scope is limited to the app.
@@feitan8745 i was joking, i think usibg netxjs is a big overkill for apis
Bro what's your font name?
Jetbrains Mono
what vscode theme is that ?
Night Wolf [black]
Why Id is string
Not a fan of having folder structure denote functionality. It feels like a breach of the idea that the functionality is in the code
Make a full video
Sveltekit is leading the way. Wow 😅😅
What the h is that arg list!?
So this ia considered to be simple
Why does it look like Laravel?🤨
Does that matter? Good ideas are good ideas.
Why the hell do you want to make an api with a Frontend framework? It's a subpar solution but people who haven't used real backend frameworks won't realize it.