This is exciting! Within the next year or two, we have been exploring creating a mobile app to pair with our web app, and even though our codebase is currently React, we're not instantly buying in on React Native, instead exploring either investing the time into building a brand new app from scratch with Swift/Kotlin, or a "wrapper-oriented" approach that lets us get super quick wins with even less time than porting over to React Native. The latter would be amazing, because our app is still young and the internal API is unstable, meaning a truly native app would be tricky, since we'd have to constantly be versioning our API to ensure things work across different versions of the backend/mobile app. This adds overhead that is pretty prohibitive. Taurify and the CN tools look awesome. We're already using Tauri for some side projects and it's been excellent - excited to see where this goes, and congratulations to the Tauri team.
All this nonsense is the never ending battle to fix JavaScript problems using more JavaScript. It will continue to grow until dissolution. The immense fragmentation and the underlying language (even with typescript) is driving me away. I have more interesting things to do with my life than to learn yet another JS tool to do a job that I already know how to do. This people are profiting from your time.
Talking about the "massive inefficiencies in the build pipeline" in vite when we shaved off 95% of the build time of our previous projects compared to vue-cli, is saying something 😂
Lol I've been working with all these features since basically right Solid Start v1.0 released, on a startup project which has grown pretty huge, now I feel like I actually kind of understand what I've been doing this whole time 😂
Unfortunately, for Vue teams, Storybook support leaves a lot to be desired since Vue support feels like an afterthought. My team ended up quickly putting together a static documentation site using Nuxt in our repo using native Vue components. There was so much more flexibility in doing it this way than jumping through the weird hoops required to use Vue within the context of Storybook. As for testing, there's no need to mix your documentation with testing. Storybook is definitely terrific for React projects, though.
I've known and been following his work since early days. this is for the first time I see him talking and feels so proud seeing him in action. thank you for your hard work and all the best.
I can't believe a PHP framework has been using Vite for over 2 years now while Next, which is one of the most popular JS frameworks today, is still stuck with something that's quite similar to Webpack
This is HUGE! Can't wait to test it out in my project. The fact that it doesn't require storybook dev server to run the test is great! I have been running storybook test in chromatic and they are very expensive. This will save me a lot of $$$
Ok this is pretty cool. I knew Storybook had some testing capabilities, but I didn't know it was so interesting. And now even more integrated than before.
