I recently switched from CRA to Vite, and oh my dear Dante it's so much faster and smoother! I even posted about it on Facebook even though 90% of my friends aren't devs and have no idea what it means, just because I loved it so much as soon as I used it. I've even started using Vite for vanilla TS projects, because setting up a TS pipeline manually is a pain.
@@nettojms5083 I do. It's how I keep in touch with most of my friends. I think of LinkedIn as a resume and job search site, not really as a social media site.
Create-react-app is not too bad, but the biggest problem is that it seems development of it has completely stopped, with no commits in months and issues growing into the thousands. Probably because facebook laid off the whole team 😅
Yeah I just started using Vite and it feels like CRA but faster and better in just about every way, it only takes literally a few minutes to get started with it, definitely recommend. Also I wasn't expecting it but this vid helped me solidify certain concepts such as static site generators and server side rendering. Thanks as always for putting out informative content that's also easy to understand. :)
I've used Gatsby for a simple marketing site and hated it (sending my form with GQL was a pain in the ass). Right now I'm learning Remix for a job interview and I'm pretty impressed so far :)
From my limited knowledge, using GraphQL for something like that is quite overkill to be honest. Any details from learning Remix that I can know of? Would love to hear more from you
@@phucnguyen0110 Yeah... it was to send data to a homemade newsletter API. As for Remix, the official docs is pretty nice, there's 2 tutorials that cover the basics pretty well, I think. :) Take care, Phúc!
nice, just fill your company with a billion different frameworks and tools that will probably be obsolete in less than an year (as history shows us) and make your projects basically impossible to maintain as almost no one knows how to use these things that were used to solve problems that usually don't exist
Next.js existed for few years already. I got to know about it few years ago, but it has already existed for a long time back then. Gatsby is pretty old too. These two will probably be the last to disappear, and probably not sooner than when React itself does. And then you can finally return back to our most beloved PHP, which would have existed for 30-40 years by then.
I personally love the ease-of-use for vite. It's really nice. Also, Svelte seems really nice. Do you have any plans on making a Svelte video? Maybe a tutorial like your react notes app (loved it btw) but for Svelte?
@@kgaming7599 this is the issue that made me not want to learn svelte, I figured vue has the best of both worlds. the availability of tutorials & jobs, the easiness of use of the framework, and the availability of extensions and dev tools and plugins etc (aka the ecosystem) and how vast it is with the growing community
It's a shame testing rarely gets any mention on this otherwise fantastic channel. Configuring Jest can often be tricky in Node/front end, and while I enjoyed the speed boost from using Vite to build my React app, I struggled to configure Jest and Istanbul to work properly. I actually ended up scrapping the Vite and going back to the older way of setting up my app, which is Babel + Webpack. Slower, but now my unit + integration tests at least run. And testing works out of the box with create-react-app, too.
I use Laravel/PHP for backend API and then ReactJS/Astro for frontend, depending on what’s required. I am still using Linux server boxes for hosting with Apache/MySQL. Laravel fits in perfectly well. Easy to set up a local dev environment with docker.
I have always used Laravel for quick back-ends, very solid software with some nice design patterns. I would however not use it if you are using Astro. If you are using Astro you are probably trying to build an optimised website and a PHP backend will be such a bottleneck, that any speed improvements from Astro will be diminished.
@@jasperams Thanks Jasper. Bit more info: Astro is for marketing/static site frontends due to SEO benefits compared with React/Vue/Svelte/other SPA. There are usually some Laravel-served api endpoints that are helpful for pulling in blog post data at build time. Laravel/PHP is primarily for backend client portal and api endpoints specifically for client/admin login pages. For management sakes, I prefer to keep separate repos for different aspects of a business site. Are you using NextJS for everything? How do you set things up?
Was wondering as well... But, no matter. This is just one person's opinion... Also, most youtube creators feel they're under pressure to appear to know about all of the latest trends and this week's js framework. This can sometimes steer people in the wrong direction. RU-vid devs likes to throw out ultimatums, I guess to trigger more comments. I wouldn't take this too seriousely. Afterall, we need to make our own decisions on what fits best for what we do. Whenever youtube says "don't do xxx", I would approach with caution...
I left a similar comment before seeing yours. I’ve both started TS CRA projects from scratch using -template typescript, and I’ve added TS to existing CRA apps, I believe with the simple act of adding a tsconfig file to the project and that’s it. I genuinely can’t imagine how it could possibly be any easier to get TS support than that.
T3 is one of the better stacks rn. It has type safety from frontend to backend. Auth and the database are 95% ready after creating the boilerplate. You only need the private keys to have it fully working. And ofcourse tailwind
have been watching your content for a while but just realized missed to subscribe. As a self tought and still learning codder, your content have been short and to the point and was a great help so far. Mach Thank you.
I still think it's still a good exercise to try and manually piece all the components together to get an understanding on how everything works at a lower level. Once you have a good understanding then certainly use a higher level framework.
Kyle, you may wanna present each of them in detail. I'm curious what Gatsby uses instead of DOM. Are those that use jQuery too slow? How compatible are they if I add Redux, Jest, AntD? Can you add the less popular alternatives and talk about them too? Have you tried UMI? The comment section here really caught my attention. Surprisingly lots of useful info from everyone.
I mean I think Gatsby is mostly made for ssr so no redux here it's mostly just static pages rendered on the server Though astro is in a bit more of a gray area
Nice overview. I would like to supplement the "take nextjs further" part by stating: redwood and blitz upgrades your stack to a full stack monolith app. Where as Remix is an alternative to Next with a different approach to ssr
I personally started with React and NextJS after years of custom building HTML/CSS and PHP OOP and I am really in love with NextJS and Typescript. P.s. great video I watch a lot of your content and you bring real value to the developer community. Thanks mate ✌
You can use next js in almost every project. You can opt for ssg and csr based on the route. Though guarding route will lead to additional steps but it's going to be a fun in next 13 once it's stable...
CRA with TS is a pain? What? Why? I'm with you, it's better to keep away CRA for new applications. But I still haven't seen a minute of video, and I see that CRA is not as bad as you say...
Moving forward use a high pass filter in an equalizer to clear muffly frequencies in your vocals. The bass in your voice is hard to ignore. Tip for a tip
Wow, incredible data! super interesting everything! Maybe put the links of all the pages that you visit for example vite, next, etc. Is just easier for us to scroll down while watching the videos and open the links right there. idk its my suggestion! The video is amazing and Ididnt knew anything that you said, so you've made my mind bigger in these minutes!
i’m about halfway into the video so idk if you mention this later, but Astro is capable of both SSR and SSG- and the SSR features it has are actually really ahead of the game. I use Next 13 and Astro both very frequently, and I think both the Next and Astro teams are doing great, but I think Astro has the best SSR of basically any full stack framework. Next could probably beat it in the world of react, but for anything else Astro is amazing. I love using it with Svelte, also the create Astro CLI is probably the best CLI experience i’ve gotten from a create experience. If you haven’t tried Astro for SSR you’re seriously missing out
Just note Astro is MPA. Not SPA like normal React app would be. That being said Astro has been a lot of fun to use. Simple and powerful and I’m a Fred fan.
I'm a longtime WordPress dev and I've been hearing about Astro as a frontend framework for a WP backend. I'm curious if React is less capable inside Astro...I read (and probably misunderstood) that it's not possible to pass event handlers between components for a truly dynamic experience. Can you use context providers, routing and other features? I'd appreciate any enlightenment. What are the limitations of React in Astro?
@@ontheruntonowhere Yeah so the number one issue with Astro is exactly this. Because it uses "partial hydration" things like context providers won't really work. Now you can get the exact same effect through what Astro calls "nanostores" they're basically just Svelte stores, but those allow you to share context in a partially hydrated environment because the nanostores live outside of the DOM nodes. They're actually really nice to work with IMO. The reason why this is a problem is because it can make portling legacy code a real pain because you'd basically have to recode a lot of the UI logic for sharing state between components. I guess the good news would be that this rewrite would allow for faster compilation and runtimes, but IMO it wouldn't be worth it to rewrite considering all the existing support for WordPress, unless u really really wanted to do it. That's why I prefer using a fine-grain reactive framework like Svelte with Astro because the two pair really nicely together because they were both built to support similar design patterns. This docs page is really helpful if you want to learn more about this: docs.astro.build/en/core-concepts/sharing-state/ TLDR: There aren't any limitations on React in Astro, but using React in Astro could require some rewrites to the React code where state-sharing logic is defined.
@@MerkieAE Thanks for this explanation, very helpful. I'm not going to be rewriting anything (at least not yet) but the WP sites I build are generally more complex than a blog or marketing site. I typically interact with the backend a fair bit and I was imagining the React islands in my pages as fully-functional standalone apps. Now I guess I have to learn Svelte, something I've been consciously avoiding until I get used to React's concepts and methodology.
Astro > Gatsby for one main reason- you can use the regular DOM, which means all those fun tutorials and student projects and documentation you may find online are much more likely to be in vanilla JS or Jquery. You can still find tons of React Docs, but I find due to being more general purpose, there's a bigger pool of code that you don't have to refactor if you stick to using the regular DOM vs virtual DOM.
I tried switching my production build to Vite but run into a problem with code splitting. Turns out that the esbuild doesn't really respect the import order, and I had parts of a library undefined, because they were reexported before they had a chance to be imported.
Hi, I'm a a trainee working on my bootcamp project. We didn't use vite or react cra during the course(we didn't even use hooks). So I'm completely new to this and scared AF. Would you mind telling me if vite is suitable for beginners?
As someone who has been around in the web dev space since the end of the 90s, I find it interesting that we went from "generate everything on the server" (PHP, ASP) to "it's too slow, generate everything on the client" (React) to "it's too slow, generate most things on the server" (Next.js). Conveniently the push back to the server appears to line up perfectly with the rise of cloud services that charge for server resources 🤣. As usual, think for yourself and don't chase the latest trend without fully understanding the ins and outs.
' "it's too slow, generate everything on the client" (React) ' 👆 this is kinda false. you're talking about single-page-applications in general and the reason for them was because server-side-rendering doesn't account for user interactions (unless you literally refresh on every click, very wasteful) and also tools like next.js will do SSR as well as load an SPA which then takes over the rendered page for near-instant navigation. also, SSR might actually drop in popularity again in the future if web bundles (server responds with document + assets to initial request) turn out great because then SSR won't have as big of an advantage as it does right now. that being said, it's true that SSR was overly neglected when it's a very important and stable approach to delivering content. the big issue in the past was mostly that there was no good way of using the same templates for SSR and for the frontend. trying to make a modern web app when you're using something like Thymeleaf or Blade on the backend is a nightmare.
@@FunctionGermany JS was working totally fine for rich interactions before SPAs. That being said I like SPAs for apps (not websites) because they don't involve a server. The CPU power of all clients together will be vastly more than any server and not cost me a dime in hosting. This is huge. I feel like SSR is pushed for ANY situation to obviously increase cloud spending (the pockets of Vercel). Too many devs use Next for apps when SPA was the better choice. I still use Next for public websites.
How…is using TypeScript a pain in CRA? There is a typescript template you can use when creating a new project if you want, but adding it to an existing CRA is as simple as adding a tsconfig file and just….starting to use TS.
Ok, I definitely prefer Next.js over CRA... BUT... the constantly changing landscape of the React ecosystem is absolutely insane. Decision fatigue, learning curves, and lack of standardization across the industry is exhausting and confusing.
Maybe because you invent constantly more and more new tools and frameworks instead of sticking to one well working one? It is community problem, which is a huge problem in frontend. People over and over bring new shiny toys, instead focusing on creation of reliable and long term sustainable apps build on one thing.
That's webdev though. Not just react. More stability in server side or thick client. But web dev is constantly crazy. I'd say it's honestly more stable these days than it was 10 years ago
and youd be wrong about that. More stable was having 5 languages to worry about, today there are literally countless codebases you can work in now and almost none of them are different enough to matter.
Just recently suggesting to move from cra to vite and my senior happy with it, once i'm using vite i feel cra is so slow although configuring eslint on vite is a bit difficult
As a frontend new developer, it's really hard for me to work..when I got confidence using some frontend technology, in few days other is coming. Does everybody feels the same?
I just said this in a dozen comments here too, its totally unfair to spend time learning something because "youtube" said to and then a week later we are told that same thing "is not good anymore" and now have to spend another week learning a different language? HOW do we expect to get any work done like this?
Been working in react for 6 years, never used CRA….earlier created a custom config for React Redux using webpack, later on pretty much switched to React BoilerPlate.
One of the things I liked about create-react-app was that it came with eslint installed. Is there an easy way to integrate eslint with Vite for React apps? Eslint is one of those things what I find tricky to set up but very useful.
Its really detrimental to release videos like these every few weeks when people are simply just trying to get a handle on what things are going to help them get a secure job in the field. CRA is still totally viable to use.
Is there some sort of library that transfers your code from CRA to Vite without endless copy / pasting? Because I am already pretty deep into the woods with CRA.
U recently posted a dynamic markdown editor on ur blog page. Is it not Dynamic ? If it is how did u build it using Gatsby or Astor for ur blog article page ?
Depends on your purpose. For starter and simple project just to learn React I suggest Vite or CRA. CRA starts to become bad when you have long and large project and there comes a time to upgrade. It was painful for me. Especially because dependency issues popping up over time and some part are hard to solve because CRA hold them. You can eject CRA but that leaves you on your own, even to the point where cannot upgrade CRA anymore. But overall, CRA is still a good option for small project. On the other hand, I used Vite not long ago for Sveltekit project. And damn, it is fast and pretty easy to use. Love at the first sight!
Hello, I am a student in data science and I would like to set up my research topic with facets for my thesis (sort of). Basically, I have data and I would like to create a site like an e-commerce site in which I return the automatic result just by making filters but no payment, just a visual of the document, author, title, etc and there I thought of react but there after following your tuto I don't know what to do. Personally I'm not too much into the world of programming. My question is the following: what do you recommend as a framework that can answer my question knowing that I want to use elastic search that I find nice and that can retrieve my data via a database.
Likely I've been using solidjs and loving it. Also dipped a bit into solidstart. It's buggy as hell and documentation is not good but otherwise really liking it. Can't wait for beta
Kyle quick question if I have a create react app how do I port it to Vite or another framework? Or any of the others? Looking for a way to port things as best I can to like Next.js.
The bigger problem with CRA is slow development cycle. They push features at an incredibly slow cycle which makes the tooling outdated compared to other stuff available in the community.
Tried to switch big project to vite from cra and build time increase to 10s. In dev mode all works fine, but after build, project just not started, only js errors. Also no ts error modals by default
I've never seen this guy's videos before. Does he have an industry job that requires him to ship code to production regularly, or does he just make RU-vid videos? I'm trying to get a sense of how much weight I should put into what he's saying.
Not a single word of parcel. It's as fast, if not faster, as vite and you don't need to configure anything if you don't want to. The plugin ecosystem is bigger and feels now grown up.
I want to recreat my blog. I plan to post weekly there. So the content will be static, but I plan to have a lot of content in the future. Would NextJS be a Overkill? What about the CMS with Astro? WOuld Astro be better choice? Thanks!
Hi, you are a great. Do you make video on creating sitemap for react app. As i have seen their is no much information regarding to these. Everyone need Sitemap and the process of applying sitemap is not available.
We have a typescript react application using CRA and this makes it basically impossible to use micro frontends because it requires the module federation plugin. My question: What way would you recommend building a react app that would allow me to use module federation plugin to add micro frontends?
thks for the vids. I'm not sure fullstack frameworks are the target in the near future. As long as there are still different technologies between different devices (android, IOS, web...), backends will remain out of the front end. For large products I mean of course.
Just learned about Vite recently, I’m still working on remembering what I need to do to use it, but when I remember it’s way better. Maybe I’ll give the rest of these a go soon.
Ok if you talk about RoR, what about php frameworks (Laravel, Yii), isn't it much easier? Or if you need quick platform for development why don't just install wordpress?
Web dev is an absolute goof show now with 100+ "frameworks" and its all dumb BS that makes like ONE thing slightly more easier to use but you have to learn an entire new syntax and codebase to use. What happened to simple JS?
I don’t like being forced into a frame work. There are always situations in the real world where you end up fighting the framework. And you end up with awful performance or terrible code. It’s like a totalitarian government that feels you what and how to do. Eventually it rubs against the people and they’ll rise up and get frustrated and the wheels come off. Openness and freedom (also to make mistakes) ultimately prevails. This is why the non-tightly packed framework language products are still there and being used and have a far longer software lifetime.
That is what i exactly like about JavaScript frameworks that everything is open ended and i can use my own logic to begin with.. that's why i prefer Nodejs over Django or Spring boot.
I come from a c# back end development and not done much front end except old school html/javascript/jquery from about 10+ years ago -- I want to learn to do react and found react + vite is the way I want to go, Do you have videos / tutorials on this and THEN turning that react app into a mobile Android app using dev/production/staging environments
I never heard an explanation of why using CRA means I am doing React wrong. Pretty bold claim. I think we all understand that any app generated from CRA needs stuff added to it before shipping it to production. I am sure it's fine for small/medium sized projects, as it has been fine for those types of apps for years until this video was made. I'm happy there newer tools coming out that may speed up the dev experience. Lastly, I've never had a problem using typescript generated by CRA. Again, I understand I will likely adjust the generated tsconfig.json file. I'm sorry to say I think videos like this one are just promoting FUD in favor of other competing tools.
I couldn't hate create-react-app more if I tried. It's so slow, installs thousands of dependencies and makes for the worst developer experience out there. I'm glad Vite exists and I will never go back to CRA.
