Capacitor and Flutter has their end coming. I swear the moment you think React and the JavaScript community is really resilient This is the only place i think using RSC is going to smash harrrrdddddd.
I have a question. As far as I understand about ShadCN/whatever Toastifier, it needs a Dom for itself to generate the Toaster Dom in document.root level. But in your Index Component, you just passed notify function as a prop without adding a Dom for Toaster, and it works. Is this because Expo "use dom" handles everything? or is there a Dom for Toaster somewhere else?
this might be a stupid question. but do we have to go down different routes if we build in web first vs native first, but have plans to eventually use both?
With Tauri + React build Web Engine Rendered Desktop and Mobile app With React Native can do the similar but with native option hope Expo support desktop build also
It’s to mirror the behaviour of native apps better I believe. If you notice with most apps you can’t select text, as there’s usually another action that can occur from a tap or hold.
how to create this project using expo dom. I fork this repo I got errror:--- ------------------------------------------------------------------------------------------------- D:\Users\expo-dom-components-canary-example>npm i npm error code ERESOLVE npm error ERESOLVE unable to resolve dependency tree npm error npm error While resolving: mdex@1.0.0 npm error Found: expo@52.0.0-preview.3 npm error node_modules/expo npm error expo@"52.0.0-preview.3" from the root project npm error npm error Could not resolve dependency: npm error peer expo@"52.0.0-canary-20240912-1059f85" from @expo/dom-webview@0.0.1-canary-20240912-1059f85 npm error node_modules/@expo/dom-webview npm error @expo/dom-webview@"^0.0.1-canary-20240912-1059f85" from the root project npm error peerOptional @expo/dom-webview@"*" from expo@52.0.0-preview.3 npm error node_modules/expo npm error expo@"52.0.0-preview.3" from the root project npm error npm error Fix the upstream dependency conflict, or retry npm error this command with --force or --legacy-peer-deps npm error to accept an incorrect (and potentially broken) dependency resolution. npm error npm error npm error For a full report see: npm error C:\Users aved\AppData\Local pm-cache\_logs\2024-10-30T07_49_34_087Z-eresolve-report.txt npm error A complete log of this run can be found in: C:\Users aved\AppData\Local pm-cache\_logs\2024-10-30T07_49_34_087Z-debug-0.log
Might finally give react native a go when this comes in. It’s always been a bit of a hurdle that you have to start near from scratch for native! Wow 🤩
This is one of the most insane things I've watched as a react-native developer in months. Looks like Expo has really been cooking lately. 🔥
This was what we all needed from the beginning.
On God
this revolutionary web devs going into mobile dev
Capacitorjs does this too
Flutter just got cooked.
can you elaborate ?
Write once, Run everywhere 🤯
Great new feature 🔥 love how you can communicate with native using props
This is great. Soon Expo will replace nextjs as the next cool thing in react. One codebase to rule them all.
i wish not man, i wish not
Super cool. Thanks for such a very helpful video.
That's so cool! I was looking for a way to use the shadcn graphs in RN
wtf! This is soooooooooooo goooooooooooooodddddddddddddd
it will reach the general public
Capacitor and Flutter has their end coming.
I swear the moment you think React and the JavaScript community is really resilient
This is the only place i think using RSC is going to smash harrrrdddddd.
I have a question.
As far as I understand about ShadCN/whatever Toastifier, it needs a Dom for itself to generate the Toaster Dom in document.root level.
But in your Index Component, you just passed notify function as a prop without adding a Dom for Toaster, and it works.
Is this because Expo "use dom" handles everything? or is there a Dom for Toaster somewhere else?
Bros eyes look like he in the clouds but good content
Can’t remember when I filmed this but I’d guess it wasn’t at a sensible hour, or I had about 4hrs sleep 😂
Will this work for nextjs ?
really interesting
this might be a stupid question. but do we have to go down different routes if we build in web first vs native first, but have plans to eventually use both?
This is amazing! It's a shame the expo-dev-client package seems to be broken in this release though. Has anyone made it work?
Whats the diff vs PWA aside from the native functions.
With Tauri + React build Web Engine Rendered Desktop and Mobile app
With React Native can do the similar but with native option hope Expo support desktop build also
i think it will lead us to put more web component than the native because it's much easier to build UI.
Can i use peerjs with this?
Capacitorjs does this too
How can you create native components in capacitor?
Does it do it better, I want to make a mobile app using webRTC, already doing a desktop app using peerjs
What if you’re on next?
I only use ionic .better full web view with native features
was made with solito??
What’s the logic behind adding NoSelect component? Anyone?
It’s to mirror the behaviour of native apps better I believe. If you notice with most apps you can’t select text, as there’s usually another action that can occur from a tap or hold.
what theme are you using there buddy?
Just GitHub Dark I believe
@@JollyCoding that explains why I like it; it's the same one I'm already using
It justs embed a webview, you guys need to chill out.
which is good enough for crud apps
haha its ionic
ionic on steroids
please slow downnnnnnnnnnnn
for non english viewers :(
Is it pronounced Hermies or Hermes? 😂
how to create this project using expo dom.
I fork this repo I got errror:---
-------------------------------------------------------------------------------------------------
D:\Users\expo-dom-components-canary-example>npm i
npm error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving: mdex@1.0.0
npm error Found: expo@52.0.0-preview.3
npm error node_modules/expo
npm error expo@"52.0.0-preview.3" from the root project
npm error
npm error Could not resolve dependency:
npm error peer expo@"52.0.0-canary-20240912-1059f85" from @expo/dom-webview@0.0.1-canary-20240912-1059f85
npm error node_modules/@expo/dom-webview
npm error @expo/dom-webview@"^0.0.1-canary-20240912-1059f85" from the root project
npm error peerOptional @expo/dom-webview@"*" from expo@52.0.0-preview.3
npm error node_modules/expo
npm error expo@"52.0.0-preview.3" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error C:\Users
aved\AppData\Local
pm-cache\_logs\2024-10-30T07_49_34_087Z-eresolve-report.txt
npm error A complete log of this run can be found in: C:\Users
aved\AppData\Local
pm-cache\_logs\2024-10-30T07_49_34_087Z-debug-0.log
@t3dotgg