Yarn workspace with React and React Native

Learn how to setup React and React Native in a yarn workspace.
Code: github.com/ben...
Links from video: / how-to-use-yarn-worksp...
----
Patreon: / benawad
----
Follow Me Online Here:
GitHub: github.com/ben...
LinkedIn: / benawad
Instagram: / benawad97
----
Join the Discord: / discord
Twitter: / benawad
#benawad
TikTok: / benawad ​
​
----
Follow me online: voidpet.com/be...
#benawad

[@Sarmadfarhankhan]

Jesus, this is what I was looking for. You're way ahead Ben 👍👍

[@flashzone9809]

Thanks Ben! Great tutorials! This is what I'm looking for. Since this video was 3 years ago, are we still using this method to setup or any new updates? Thank you!

[@andresmontoya7852]

Well.... I prefer to wait when react and react native support perfectly that option of yarn without all that configuration :).

[@flashzone9809]

Any updates on this? Any solution without configuration?

[@thelavishcoder2553]

Would this work in production?

[@nishmamaskey1093]

Thank you for the great tutorial!
Is there a way I can add "Material-UI" dependency under "peanut/common" and use it in many static create-react-apps under "peanut/server" folder?

[@bawad]

you could import material ui and export it from "peanut/common"

[@akashshrestha01]

nepali?

[@zemielasma8986]

Awesome!

[@jasonshen]

very nice video cheers

[@DrPanesar]

Hi Ben, For the next major project i wonder what you think of using Next JS for the front end rather than create-react-app? I've been using Next JS for my front end clients for a while now and its a really excellent tool that gives you the best of react and server side rendering built in which is awesome for SEO amongst other things. For a production from end i think its hard to beat.

[@bawad]

I'm not totally convinced server side rendering is worth

[@DrPanesar]

Ben Awad the difference in google search rankings with server side rendering convinced me it was worth it. When you get to production it really makes a big difference. The server side rendered page also allows better linking to your pages but external sites or social media. I was trying to setup next js with yarn workspaces but could get that to work yesterday.

[@bawad]

There definitely are benefits to ssr, but I would rather not deal with the added complexity. And some of the things can be mitigated:blog.jakoblind.no/is-ssr-worth-it/

[@WSRast]

@@bawad I think you're right about the added complexity, but the link you give doesn't really mitigate the things SSR purports to solve. Saying SEO is okay because Google supports JS-rendered sites, then saying others like Bing do not (maybe they have since that was written) doesn't address the problem; it just argues the problem isn't as bad. Showing dummy content is also no replacement for real content--you can't read dummy content.
He also doesn't go into the benefits of fetching data to prefill the page on the server. That's something that will be a lot faster from the server than it would generally be from the client. You're saving the user a round trip like that.
Tackling SSR in a manually configured Webpack project was, for me, a real beast of a task. I'd encourage anyone who feels the need for SSR to look for a prebuilt solution, one of which is Next.js. You really don't want to deal with setting all that up yourself. I certainly will avoid it at all costs.
I really do like the decision tree flow chart on that page, though. I think many trying to decide whether to tackle SSR or not would be well-advised to go through that, if only to gain some foresight about what they're getting into.

[@bawad]

yeah some sites really benefit from ssr and would be much worse with client side rendering

[@oroneki]

Great. The typescript version is comiiiing! :)

[@sam-zc5ku]

I have two react native apps, the app solution won't work, any other solution?

[@bawad]

Not that I know of

[@bloggervista]

too much complicated

[@bawad]

I agree