Stop Using Create React App

Поділитися
Вставка
  • Опубліковано 20 лип 2024
  • Create React App is an incredible tool that made it easy to setup and work with React, but as the years have gone by CRA has become less and less useful to the point that you should pretty much never use it. In this video I talk about all the alternatives to CRA that you should consider using instead.
    📚 Materials/References:
    Astro vs Gatsby Video: • Why I Switched To Astr...
    My Blog: blog.webdevsimplified.com
    🌎 Find Me Here:
    My Blog: blog.webdevsimplified.com
    My Courses: courses.webdevsimplified.com
    Patreon: / webdevsimplified
    Twitter: / devsimplified
    Discord: / discord
    GitHub: github.com/WebDevSimplified
    CodePen: codepen.io/WebDevSimplified
    ⏱️ Timestamps:
    00:00 - Introduction
    00:27 - CRA Cons
    01:14 - Vite
    02:27 - Astro/Gatsby
    04:43 - Next.js
    06:54 - Full Stack Frameworks
    #CRA #WDS #React

КОМЕНТАРІ • 492

  • @ProwlerDigital
    @ProwlerDigital Рік тому +525

    You can’t make us stop!!!!

    • @Wanderlauch
      @Wanderlauch Рік тому +70

      I'm gonna tell your mom!

    • @ProwlerDigital
      @ProwlerDigital Рік тому +49

      @@Wanderlauch I’ll just learn nextJS while I’m grounded ¯\_(ツ)_/¯

    • @kgaming7599
      @kgaming7599 Рік тому +28

      "us" - you're alone, mate

    • @danitho
      @danitho Рік тому +1

      🤣

    • @zlackbiro
      @zlackbiro Рік тому

      You sre stupid if you using CRA over Vite... LoL! You will probably be fired from my company once we see react-scripts in your package.json.

  • @jeremyt1273
    @jeremyt1273 Рік тому +21

    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. :)

  • @mifino
    @mifino Рік тому +275

    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 😅

    • @echobucket
      @echobucket Рік тому +5

      Are you just speculating, or do you have a reference for this?

    • @cryMoreLoL
      @cryMoreLoL Рік тому +13

      It’s huge, slow, and outdated- that’s plenty of reason to stop using cra when better options out there.

    • @knowledgenews5343
      @knowledgenews5343 Рік тому +3

      Are you sure? The last commit was in September, just a few months ago.

    • @indiging8330
      @indiging8330 Рік тому +34

      @@knowledgenews5343 "no commits in months" you literally just proved his point

    • @alex-dk2rj
      @alex-dk2rj Рік тому +5

      @@indiging8330😂

  • @ravenbergdev
    @ravenbergdev Рік тому +5

    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

    • @xantari79
      @xantari79 Рік тому +1

      Maybe just use angular instead? Seems google has kept things up to date better than react at this point?

  • @weho_brian
    @weho_brian Рік тому +16

    Me: Literally following documentation
    UA-cam: You're doing it wrong

    • @rwspear
      @rwspear Рік тому +1

      This video should not be taken as gospel...

    • @CristianKirk
      @CristianKirk Рік тому

      The frameworks bubble is blowing up. People will have to actually learn web development. xD

    • @dikamilo
      @dikamilo Рік тому +5

      Documentation is written by devs, UA-cam videos are from influencers.

  • @alexgochenour8740
    @alexgochenour8740 Рік тому +22

    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.

    • @David-hl1wo
      @David-hl1wo Рік тому +1

      Honestly, Vite makes things so much more complicated but it's only saving grace is that it's faster

    • @disruptive_innovator
      @disruptive_innovator 10 місяців тому +3

      i'm kinda new to all this but isn't Vitest better for Vite?

    • @MegaMetallica4ever
      @MegaMetallica4ever 10 місяців тому

      @@disruptive_innovator Vitest is basically Jest for Vite.

    • @Pilosofia
      @Pilosofia 7 місяців тому

      Vitest.

  • @zyriab5797
    @zyriab5797 Рік тому +20

    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 :)

    • @phucnguyen0110
      @phucnguyen0110 Рік тому +4

      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

    • @zyriab5797
      @zyriab5797 Рік тому

      @@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!

  • @IceMetalPunk
    @IceMetalPunk Рік тому +94

    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.

    • @ontheruntonowhere
      @ontheruntonowhere Рік тому +3

      Agree! I'm a WordPress dev and I've started using Vite as the build tool for my themes and plugins. It's great.

    • @nettojms5083
      @nettojms5083 Рік тому +4

      Do you still use Facebook? Could've posted on LinkedIn and it's doable to have connections with most devs there.

    • @IceMetalPunk
      @IceMetalPunk Рік тому +4

      @@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.

    • @carldrogo9492
      @carldrogo9492 Рік тому

      What's TS?

    • @hermit41
      @hermit41 Рік тому +8

      @@carldrogo9492 i think he means TypeScript

  • @marcosevaristo6119
    @marcosevaristo6119 Рік тому +55

    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

    • @DavidWimbley
      @DavidWimbley Рік тому +14

      For real, oh now my react app builds 500ms quicker than before, I saved so much time! This is why the javascript ecosystem is a dumpster fire.

    • @user-ik7rp8qz5g
      @user-ik7rp8qz5g Рік тому +3

      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.

    • @ihsanpro9406
      @ihsanpro9406 Рік тому +1

      @@user-ik7rp8qz5g next JS cannot be used for every type of app. It performs doggshit when you have a complex app

  • @piotrnowakowski5385
    @piotrnowakowski5385 Рік тому +4

    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.

  • @hailedagmawi8109
    @hailedagmawi8109 7 місяців тому

    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.

  • @kgaming7599
    @kgaming7599 Рік тому +91

    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?

    • @seyseyseysey
      @seyseyseysey Рік тому +4

      I hope he does. Most of Svelte tutorials are kinda outdated so it would be really nice

    • @kgaming7599
      @kgaming7599 Рік тому

      @@seyseyseysey Hah, I can't even find a tutorial, let alone an outdated one.

    • @brhh
      @brhh Рік тому +4

      @@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

    • @kgaming7599
      @kgaming7599 Рік тому

      @@brhh Yeah, makes sense. Svelte seems really powerful though. You should give it a chance! ;)

    • @732brudder
      @732brudder Рік тому +5

      @@kgaming7599 Svelte has really awesome documentation and lots and lots of examples and tutorial content on their site.

  • @zombiefacesupreme
    @zombiefacesupreme Рік тому +24

    I'm currently in the middle of converting my e-commerce site from NextJS to Astro and SolidJS and it is INSANE how much less JavaScript it uses.

  • @nedgrady9301
    @nedgrady9301 Рік тому +6

    0:52 What's the rationale behind the statement that typescript is a pain with CRA? Haven't felt any pain specifically using ts + CRA personally!

    • @digitalkoh
      @digitalkoh Рік тому +1

      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.
      UA-cam 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...

    • @bass-tones
      @bass-tones Рік тому +2

      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.

  • @sideshowlol
    @sideshowlol Рік тому +11

    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.

    • @jasperams
      @jasperams Рік тому

      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.

    • @sideshowlol
      @sideshowlol Рік тому +2

      @@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?

  • @Xe054
    @Xe054 Рік тому +2

    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.

  • @JeronimoGinaca
    @JeronimoGinaca Рік тому

    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!

  • @szalailaci3722
    @szalailaci3722 Рік тому +13

    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.

    • @imfastboi
      @imfastboi Рік тому +1

      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

  • @timehrhardt8410
    @timehrhardt8410 Рік тому

    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?

  • @BartMolkenboer
    @BartMolkenboer Рік тому +11

    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 ✌

  • @abdullahbinazeem54
    @abdullahbinazeem54 Рік тому

    Hi Kyle! Thanks for the update and stay blessed

  • @xenialxerous2441
    @xenialxerous2441 Рік тому

    Hey Kyle! Great video once again, very informative abd useful. Thanks a tonne ✌🏻🥂

  • @abdoulkarymtraore4466
    @abdoulkarymtraore4466 Рік тому +1

    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.

  • @bass-tones
    @bass-tones Рік тому +2

    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.

  • @SilverSlayer23
    @SilverSlayer23 Рік тому

    Congrats on the new home! I mean I think 🤔. Your setup reminds me of a "just moved in" feel. Still filling the home up kind of thing.

  • @AK-fb7zn
    @AK-fb7zn Рік тому +1

    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.

  • @nightshade427
    @nightshade427 Рік тому +3

    Astro is fullstack as well now much like nextjs/remix/etc, it has ssr, api routes, edge function support, etc

  • @AlanDeveloperz
    @AlanDeveloperz Рік тому

    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!

  • @j946atFIVEFOUR88AA
    @j946atFIVEFOUR88AA Рік тому +18

    i've built a couple apps with the T3 stack and it's been fun learning tRPC, works great with nextjs and prisma

    • @neneodonkor
      @neneodonkor Рік тому

      What the heck is a T3 stack? Have seen it floating around.

    • @vladislavsmolyanoy
      @vladislavsmolyanoy Рік тому

      @@neneodonkor an amazing fullstack framework built on top of nextjs with full typesafety.

    • @0MaXxXiMuS0
      @0MaXxXiMuS0 Рік тому

      They just cam out with a docs and the newest tRPC integrated. I am moving to that next after I finish what I am building now

    • @universe_decoded797
      @universe_decoded797 Рік тому +3

      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

    • @AlexM86
      @AlexM86 Рік тому

      You'll never see Kyle covering the t3 stack cause he has beef with Theo. I'm still waiting for the day these two shake hands and call truce

  • @floemizu
    @floemizu Рік тому +2

    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

  • @LaidbackAk
    @LaidbackAk Рік тому +4

    For small projects and static sites, esbuild is a good choice. It is extremely fast. Only downside for me was lack of hot reload.

    • @AugustoFnrd
      @AugustoFnrd Рік тому +10

      vite uses esbuild

    • @noopurp123
      @noopurp123 Рік тому

      Vite uses esbuild and it has hot reload

  • @muhammadharis2205
    @muhammadharis2205 Рік тому

    Which will be good for the erp system of a factory ? I'm confused which one to choose. Anyone have some recommendations?

  • @MerkieAE
    @MerkieAE Рік тому +4

    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

    • @ryanquinn1257
      @ryanquinn1257 Рік тому +3

      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.

    • @ontheruntonowhere
      @ontheruntonowhere Рік тому

      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?

    • @MerkieAE
      @MerkieAE Рік тому +1

      @@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.

    • @ontheruntonowhere
      @ontheruntonowhere Рік тому

      @@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.

  • @pro-verstka
    @pro-verstka Рік тому +1

    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

  • @rathma9210
    @rathma9210 Рік тому +16

    I think your video is aimed at hobby developers. CRA is completly fine for huge projects. It is one of the most stable and reliable toolset.

  • @stillready6405
    @stillready6405 Рік тому

    What would be the recommendation if I want to build a next js app, but only want static sites? Should I use Astro instead?

  • @symanhnguyen6631
    @symanhnguyen6631 Рік тому +3

    so what should i do to create a new react project? i am new to React-JS, please guide me, thank you very much.

    • @jordiyaputra8359
      @jordiyaputra8359 Рік тому +1

      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!

  • @KoyFoster
    @KoyFoster Рік тому +2

    For a while, this subject is something I've been looking around for. Thanks for putting this out.

  • @bryson2662
    @bryson2662 Рік тому

    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

  • @vinebe5291
    @vinebe5291 Рік тому +1

    Hello Kyle, it's false in 2:17 now you have ssr support in the cli tool of vite it's not like nextjs or remix but now we can do that

  • @gbroton
    @gbroton Рік тому +1

    How often do you have to use CRA? Is the creation of X new tools on top of it worh it?

  • @donmikkodanm.olmillo8154
    @donmikkodanm.olmillo8154 Рік тому

    I love your videos, i gotta question tho, is express still relevant? since Nextjs can do everything and has support on SSR?

  • @russobradock
    @russobradock Рік тому

    So, if i start a new project to control sales, products, customers, nexts will have better performance, using SSR?
    I am planning a big change from delphi to web, testing react and node.js, but any idea i will look :)

  • @underflowexception
    @underflowexception Рік тому +22

    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.

    • @underflowexception
      @underflowexception Рік тому +1

      @@internet4543 yup or in the context if using a meta framework eg next,astro but the same concepts apply

    • @j2ee123
      @j2ee123 Рік тому

      If you have the time, that is

  • @sudo576
    @sudo576 Рік тому +2

    I really like nextJs but the market only asks for CRA

  • @bipinmaharjan4090
    @bipinmaharjan4090 Рік тому

    Also using next js for client side application is such a pain. It does not allow to add route guards easily.

  • @jeromealtariba7339
    @jeromealtariba7339 Рік тому

    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.

  • @keytronbrown8727
    @keytronbrown8727 Рік тому +4

    I still don’t understand what’s so bad about CRA even after watching this.

  • @ahsanshafi6970
    @ahsanshafi6970 Рік тому

    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.

  • @CodingAfterThirty
    @CodingAfterThirty Рік тому +1

    Great video. I have been really enjoying Remix lately.

  • @adityanayak20
    @adityanayak20 11 місяців тому

    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 ?

  • @MrMinaAnton
    @MrMinaAnton Рік тому +1

    Another great video and just in time for me, I'm moving from CRA to Vite, I faced several problems with Material UI that I depend on it and have my own components based on it, after a search I found that these issues are common with both of Vite and Remix, any idea or workaround to use Vite with MUI? Thanks

    • @tasin5541
      @tasin5541 Рік тому

      What problems are you facing with vite and MUI? I'm working on several enterprise projects that use vite and MUI.

    • @MrMinaAnton
      @MrMinaAnton Рік тому

      @@tasin5541 First Thank you for telling me that there is hope, for me, it works fine on the localhost, but once hosted I got "TypeError: u.map is not a function", I host on shared hosting on "Hostinger", after searching for a solution I knew that this is a common issue with BOX, ICONs components from the MUI, this link discusses the same problem with someone else but the suggested solutions didn't work for me. (I removed the link as UA-cam deletes my reply because of the link)

    • @tasin5541
      @tasin5541 Рік тому

      @@MrMinaAnton you can share the link by putting a space before the dots (.)

    • @MrMinaAnton
      @MrMinaAnton Рік тому

      @@tasin5541 Looks like UA-cam AI is so smart, please add /mui/material-ui/issues/31835 after GitHub main url

    • @tasin5541
      @tasin5541 Рік тому

      @@MrMinaAnton I faced this problem once. Try deleting the node_modules folder and reinstalling the libraries again. Also stop the vite server first. Trivago/prettier-plugin-sort-imports library to always keep mui imports high in your import lists.
      This is my prettier config
      {
      "arrowParens": "always",
      "bracketSameLine": false,
      "bracketSpacing": true,
      "embeddedLanguageFormatting": "auto",
      "endOfLine": "crlf",
      "htmlWhitespaceSensitivity": "css",
      "importOrder": ["^[react*]", "^@mui/(.*)$", "", "^[./]"],
      "importOrderSeparation": true,
      "importOrderSortSpecifiers": true,
      "importOrderCaseInsensitive": true,
      "insertPragma": false,
      "jsxSingleQuote": false,
      "printWidth": 120,
      "proseWrap": "preserve",
      "quoteProps": "as-needed",
      "requirePragma": false,
      "semi": true,
      "singleQuote": true,
      "tabWidth": 2,
      "trailingComma": "es5",
      "useTabs": false,
      "vueIndentScriptAndStyle": false
      }

  • @digitalpartner7598
    @digitalpartner7598 Рік тому +1

    hi bro, can we setup an activation license key for react app , if yes how? thank you

  • @saulblancotejero8298
    @saulblancotejero8298 Рік тому +1

    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...

  • @studyingasyouwere
    @studyingasyouwere Рік тому

    Thank you for your interesting video. Useful insight before I start creating more web dev content ☺

  • @anassnassim
    @anassnassim Рік тому

    i have big issues with my project it take too long to run or start
    any help from you guys

  • @mojosmoke
    @mojosmoke Рік тому +1

    That's all well and good, but when are we gonna get some guitar tutorials featuring the background Jackson? Give it a high z-index already!

  • @maulanasodiqin6693
    @maulanasodiqin6693 Рік тому +1

    i use vite + react for production project and is Amazing, both DX experience and user Experience

  • @bogdanma102
    @bogdanma102 Рік тому +1

    how do you know what somebody need? thank you

  • @heindiez
    @heindiez Рік тому +4

    I have been using Nextjs for quite a while now on multiple projects and its really good.

    • @rajeevanand111
      @rajeevanand111 Рік тому

      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...

  • @romievthedon
    @romievthedon Рік тому

    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

  • @JamesMooreSeattle
    @JamesMooreSeattle Рік тому

    Any thoughts for what to use when building a chrome extension?

  • @elij8852
    @elij8852 Рік тому +1

    These are great suggestions. I've been using CRA for too long. Time to switch.

  • @raj.blazers
    @raj.blazers Рік тому

    What is a static site? If a spa has api calls fetching data and spa renders it, will it be considered as static site?

  • @bipinmaharjan4090
    @bipinmaharjan4090 Рік тому

    Tried vite for a project my only complain is it do not export code in commonjs format. It alway export code in module.

  • @duey121
    @duey121 19 днів тому

    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.

  • @saketaryan2227
    @saketaryan2227 Рік тому +2

    Also in Next Js , You can do ssg with ISR !!

  • @yinonelbaz5309
    @yinonelbaz5309 Рік тому

    Very helpful content! Thanks for the amazing channel!!!!!

  • @shadowsbane171091
    @shadowsbane171091 Рік тому

    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.

  • @MrNewRevolutionary
    @MrNewRevolutionary Рік тому +1

    I wish my life was as well put together as this guys hair

  • @JuicyBenji
    @JuicyBenji Рік тому

    Okay I hear ya, but I’m already in too deep with my CRA app, so maybe you could make a video on how to transition from CRA to next.js?

  • @bohdan4677
    @bohdan4677 Рік тому

    Are there sites built with next.js and providing high web vitals? Give me links please.

  • @thequang9234
    @thequang9234 Рік тому

    Hoping you could do a tutorial on developing a blog like yours :)

  • @Fe6b0lA
    @Fe6b0lA Рік тому

    Vite is so awesome. Spinning up a react app in seconds is so cool. CRA takes wayyyy too long.

  •  Рік тому

    As always, everything in two words. Awesome.

  • @muhamadfirhat3689
    @muhamadfirhat3689 Рік тому

    I hope there is a way to migrate from CRA to the alternative with minimal effort. Because dig in into a tons of components on the old project will be painful.

    • @AveN7ers
      @AveN7ers Рік тому

      Very easy to switch to vite. I switched just 2 weeks back

  • @aaronharvey5625
    @aaronharvey5625 Рік тому

    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.

  • @XCanG
    @XCanG Рік тому

    I'm stopping at Vite + React/Vue + TS because I have backend written on other language, so other tools are not suited for me.

  • @valerieosei5312
    @valerieosei5312 Рік тому

    Been wanting to dive into next.js for a while. I think this is the sign

  • @arjunchokkamaman1945
    @arjunchokkamaman1945 Рік тому

    As a Canadian resident the thumbnail really excited me for a minute

  • @AlThePal78
    @AlThePal78 Рік тому

    Do you prefer typescript or javascript

  • @kamasahdickson1549
    @kamasahdickson1549 Рік тому

    I don't understand all this, am I still going to write react? Are this Gatsby,Astro and Next js just going to make make projects fast??

  • @konradlesniak492
    @konradlesniak492 Рік тому

    I love your videos and knowledge :)

  • @kurraz
    @kurraz Рік тому

    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?

  • @adventurer2395
    @adventurer2395 Рік тому +1

    So what problems does Vite solve that CRA can’t do?

  • @screen-looker
    @screen-looker Рік тому +2

    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.

    • @hamm8934
      @hamm8934 Рік тому +5

      Then why are you watching a react video? Your comment should be: vanilla js dom manipulation > react

  • @prayogaluphalithalu4305
    @prayogaluphalithalu4305 Рік тому +1

    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?

    • @RILCOMusic
      @RILCOMusic Рік тому

      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?

  • @developer_hadi
    @developer_hadi Рік тому

    I'm planning to learn next after finishing react

  • @allinonetech2256
    @allinonetech2256 Рік тому +1

    Hi, Can you suggest me, flutter, i am confused react or flutter? I want to learn flutter. Flutter is best or react in these days?

  • @RILCOMusic
    @RILCOMusic Рік тому +29

    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.

    • @kingv30
      @kingv30 Рік тому +1

      Yeah we should wait at least 6 months before we release videos about the current landscape

  • @gustavocatalasverdrup
    @gustavocatalasverdrup Рік тому

    Hi there, Are U gonna give a tutorial on next.js? I´m looking forward to it

  • @harag9
    @harag9 Рік тому

    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

  • @anand_dudi
    @anand_dudi Рік тому +1

    Waiting for your next Nextjs tutorial

  • @ekchills6948
    @ekchills6948 Рік тому

    I recently realized this. Thanks for instilling it again. I use vite

  • @carlosricardoziegler2650
    @carlosricardoziegler2650 Рік тому +15

    Vite and Vitest are amazing and simple to setups. I like the Dev experience with these tools.

    • @Soulis98
      @Soulis98 Рік тому

      Is Vitest better than jest?

  • @Th3Younesse
    @Th3Younesse Рік тому +4

    hey, can you make a video about react layout vs using the html css layout in react ?

    • @blackpurple9163
      @blackpurple9163 Рік тому

      You mean plain HTML CSS vs jsx?

    • @Th3Younesse
      @Th3Younesse Рік тому +1

      @@blackpurple9163 no i meant using a react layout package vs jsx (html and css) react

  • @mahdibayat7555
    @mahdibayat7555 Рік тому

    hi and thank you, can you create a video specific for NextJs and

  • @andrews8733
    @andrews8733 Рік тому

    I'm sold, now how to migrate a moderate sized react SPA to vite is the question.

  • @thiccboi6211
    @thiccboi6211 Рік тому +7

    We are using a large B2B app built using an old CRA version in our product. We make around 60-70 million MRR in this product and we will continue to do so. Any claim that CRA is wrong is utterly stupid. It still works just fine. Vite is great and fast but its no where compared to the flexibility of webpack.
    If we are starting the project today we would prefer Next.js but it doesnt mean CRA is wrong. Please validate tools using valid reasons and not hype.

    • @johnkucharsky6927
      @johnkucharsky6927 Рік тому +1

      I don't think he adresses professional developers. For beginners it's interesting. This is actually strange question from the start. You don't choose framework when you start to work for a company. I use cra, because they told me to do so

    • @thiccboi6211
      @thiccboi6211 Рік тому +5

      @@johnkucharsky6927 Yeah thats the point. It still works and you make money. The beginners are watching videos like this and come to us and say lets rewrite all modules in so and so framework/tool and its going to be awesome. Its frustrating to school people repeatedly. We have added a special page in our onboarding docs to address this

    • @c7rsed118
      @c7rsed118 Рік тому +1

      @@johnkucharsky6927 If your company is small or you are lead you can choose. I work at small company and i can use for new projects what i choose (of course with consultation with team). Also for framework React Remix seems interesting, but Next.js works perfectly and production ready.

    • @RILCOMusic
      @RILCOMusic Рік тому +1

      @@thiccboi6211 exactly this, as someone trying to learn, its SO discouraging to come to youtube EVERY week and see a different video bashing the codebase I just spend a week trying to learn. Everytime I feel like im on a good track to learn a useful thing, someone has to make a video claiming that thing is now obsolete.
      Its so impactful for students when they see the thing they chose to learn is being called bad for no real reason. Now I dont know if I should continue learning React or not.

    • @wbharris1031
      @wbharris1031 Рік тому

      @@RILCOMusic I agree

  • @bruhman4008
    @bruhman4008 Рік тому +4

    For a newbie like me CRA is an absolute go to

    • @CH-tv1cy
      @CH-tv1cy Рік тому +1

      Learn the basics then switch to nextjs as soon as possible

    • @bruhman4008
      @bruhman4008 Рік тому +1

      @@CH-tv1cy i do have plan on learning NextJS soon, once I atleast build a functional app with react