This is fantastic!!, been banging my thick DEV head on a brick wall for the last two months trying to get shopify, react & express- node running in Plesk! This video and the narrator is so articulate and chilled out, 5 Stars and many thanks for taking the time to explain this to us muggins.
This is what i have been looking for years very simple and straight to a beginner. I have been a developer for years but its been hard for me to understand react but this video has done the magic. be blessed 👏👏👏
This is a brilliant video that explains how to (1) deal with CORS errors, (2) enabled, by way of the solution, hiding API keys in the server side .env. file because now there is a server in which they can be hidden. No other video / web site explains the problem when your front end has to access a third party API server, and to do both (1) and (2) you need an API proxy server. Very, very good and well explained solution that no one out there seems to be dealing with, even though the 'man in the middle' API proxy must be a common scenario, Excellent job.
Great tutorial. Thanks a lot. It will be great if you can show us how to move this to git and automate the build process and deploy this to Amazon ECS container to have the whole stuff works from ECS. And also, can we add any authorisation check in express before serving the index.html file?
Excellent video! Concise and to the point -- and no scripting errors in my program! Five Star Rating from me. Looking forward to seeing more of your great tutorials. Cheers!!
great tutorial. one question: does your method compromise and expose secret apikeys and process.env variables? (i.e. now is everything at 8080 bc there is no proxy, so it's visible for the frontend and may steal the apikeys). this is important to be clarified. thank you very much.
No. only the index.html will be served to the browser. And you can keep all the secret api keys in express server and use them when you call other apis from express server to get the data and you can send the result data to browser.
Try "npx create-vite-express", that is similar with laravel+inertiajs+react but only express as be and react as fe. You have no need to run build command every file modified in react
I hope Universe will bless your kind heart, you saved me, i was having this huge problem with my frontend React App deployed on Netlify and my backend express app deployed on Render .. I lost a lot of hair stressing out why i can't see cookies that i was setting for the frontend ...it was because the domain was not the same .. and i can access cookies only if the domain is the same .. thanks bro
Hi there, I'm just here to offer some constructive feedback. This video starts in the middle of no where. I would suggest maybe that next time you give some context as to what you are doing and how you will be doing it, that would be much more helpful. Thanks
I just start learning React and Next Js and I was wondering how I could make a very reusable button component so that I couldn't re-style it if I needed a different button style. And man THIS IS HUGE for me 😁 Thank you for the time you spent to share all of this to us
Great video thank you very much, just one question. im trying to implement this approach with nextJS (following your course) i did all the layouts and pages in folder structures as you said, but i am running a problem when trying to pass a function through the onClick prop. i think next is limiting it but i am not sure, how do i make things click? thanks :D
hello, are you marking your buttons with "use client" directive? In Next.js components run on server by default, to make a component run on client you have to add "use client" at the start of the component file.
hi @@bloodylupin, actually i did try it out but it didnt work, it felt like it did nothing really, like next.js straight up ignored it. thanks for the reply :)
Insomnia gave me back "test" but the terminal is not giving me back the data. I have double-checked all my code. Any ideas? Has the development environment changed?
