Creating APIs with Next.js: Master Next.js Tutorial #15

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


------------
Don't forget to subscribe and like the video if you enjoyed :)
Рекомендации по теме
Комментарии
Автор

thank u
I'm a self-taught front-end dev, I learned all front-end technology HTML CSS SASS js ES6 jQuery and React and it took me 2 years of learning, and React alone 8 took me months so I have a solid knowledge of this stack.
now after going deeper into the React world I see ppl saying server-less and head-less graphql really I don't know what is these things and before go to learn them I want u to guide me on where to start from should I go to AWS! it sounds like front-end stack getting more deeper into back-end

aseel
Автор

Thanks for sharing. It is a amazing and valuable series of Video regarding Nextjs

hamidja
Автор

how to handle post, patch, delete etc ?

mdridoy-efpw
Автор

Can we set up express server in the API? anyone has any experience with that?

GameCrawl
Автор

I love you mehul. Thanks for this video, this is a gem for me. ❤

sourabhmahato
Автор

Is it necessary to include the Next parameters and not just function(req, res) ?

garbjorn
Автор

How do we create the HTML or EJS template for the email or pdf in the backend?

nishantkumar
Автор

Do you know if web sockets (socket-io) can be used with the Next API routes or do you need to setup a custom express server?

jii
Автор

Please make a new course on nextjs sir

Mobilemaniaplays
Автор

Hi. Thanks for this great series.
After watching this episode, I thought that it won't be good if people can have an access to api urls.
So I came up with a question.
How do you prevent people trying to access api urls directly on the browser address bar from seeing what the api url is supposed to return?
I mean, how do you redirect people accessing api urls to some other pages, like 404 page, without letting them see whatever the res.json() returns?

Justin_Min_