Vue Contributor Days

live on youtube not just yet okay now we are live on youtube oh god oh god wait wait no i need to do makeup well let me go ahead and send everybody the link for the live stream because nobody knows we're here yet so there we go and you all can join the youtube as well if you want to um hang out in the chat simone will be moderating on our side all the different questions and things like that so um and if you guys want to you know answer questions in the chat that is totally fine as well but that link right there you can always also share on social media if you like the limitations of live streaming and all the different potential platforms you can use it's always a fun adventure and somebody needs to solve all right well let me go ahead and share my screen really quickly if i can find a gal all right can everybody see my screen does it look okay is it small well welcome everybody to view contributor days so excited um just like maya was just talking about uh missing conferences oh my gosh i think we all do and i think that's why i contributed as it has been even more interesting and more fun uh this past year and a half or so because it's just such a great way to like connect and hang out and you know i think we all miss like the speaker speaker room conversations and the hallway tracks and things like that so um and the innovation that comes out of that so really really excited to do a few contributor days um thank you so much evan for uh just you know always being open and and like you know using this as a platform to like gather feedback and you know just do this with us so do you have any like quick view like updates or whatever you want to say on this slide that you won't say on your other slides um not really yeah thanks for uh always providing this platform yeah last time uh it was uh we had some really really constructive outcome so hopefully this one will too yeah totally totally so um thinking this.labs i love that you know the work at this.labs enables us to be able to do all the community stuff because if i could just do community stuff 24 7 or maybe like 24 7. yeah 24 7 is right yes then i totally would um at this start we're about a 50 consultancy we love our clients i think one of the most exciting things we're doing right now is helping wikimedia with their view migration which is really fun but if you like working on new modern technologies and working with really cool and fun companies and solving hard problems definitely email us anytime this is how i make friends so jobs at this.co and always happy to have a little chat with y'all upcoming events um and if actually that's next week my gosh next week we have a state of angular happening uh for uh those women in tech or if you know women in tech definitely get them to join us for the monthly mentoring that we do um it's a closed space for an hour just to chat whatever level you are it's something that we're really passionate about doing uh then we'll have state of microservices a little later on in the month and then we will also have state of accessibility so definitely tune in on those if you're not familiar with some of the other events that we do um today we have i'll be one of your hosts my name is tracy you can follow me on twitter at ladyleet and i'm the ceo of this thought labs and then evan of course uh creator of bjs and lucky human to be able to do open source full-time amazing uh and then simone as well who is a uh software architect at this dot and simone has actually gathered a ton of questions from the community so again if you're listening as well definitely um feel free to ask questions in the chat and we will get to them as quickly as we can um but thank you simone also for gathering uh a bunch of different questions from the community and thank you so much for all the panelists who have uh decided to spend some time with us today the conversations are going to be amazing we're going to have community updates and everything like that um if everybody just wants to do like a quick 10 second introduction to yourselves uh maybe starting with ben would just go down the list sounds good hello everybody uh so yeah so my name is ben i'm a staff developer experience engineer at netlify and do a lot on the core team as far as like docs and community organizing so yeah happy to be here um i'll pass the ball to rahul hey i'm rahul i'm a soft engineer at grammarly and uh i work in their own core team mostly in compilers i don't think ah do you thought question mute uh my name is thousand bloombog i work as a product owner so so i'm i'm leading an engineering team working at a customer portal for amphiphonemic in germany uh and i'm a review core team member uh working here and there and everywhere very prominent on discord if you have a question i try and pop in hi my name is kim show and i'm part of the view code team and i mostly work on as part of your container as you work on the view devtools on the view ui answer me next yeah and hello yeah my name is anthony and i'm a team member of view and the vid so i used to work on open source full time and now i enjoy just joining uh nux navs next slabs for doing the vehicle integrations for knox 3. so yeah that's all for me john hi um john leader i'm the author and founder of beautify and yeah that's it hi uh i'm uh it's my turn i guess so uh hi i'm kia i'm also a viewer team member and my main focus is ux and also walking around with beatpress as well and maybe some new stuff is coming on to beatpress too so stay tuned uh next is hao kung jing uh hello uh i'm ho chi chang and i'm also a car team member of the real team and the evita team uh i'm the full-time open source developer in the real team and my focus is on futurist build tools including build cli and now i also work on vit related stuff and that's for me okay hi my name is kataka uh my i'm a team member thank you and uh yeah we start off with daniel for the next hi i'm daniel rowe i'm on the core team of nuxt which is pretty cool okay okay uh i'm phil prakowski i'm cto co-founder of use storefront i'm particularly interested in e-commerce and performance so you also may know me from my conference talks about web performance or a serious musical about web performance hey maya okay hi everyone i'm maya shirvin and i'm a senior software engineer at microsoft and i'm also a quality member of the storefront ui and i'm also a nuts ambassador that's a lot and jonathan hi everybody uh my name is jonathan i'm a creator and maintainer of chakra uiview and i'm also a ui engineer and engineering manager at rcta.ai and i'm also a positive member of the store from europe over to you yeah i'm sorry my name is i'm a team member of views and i also work for next labs on the lucas project your town carlos hello my name is carlos i'm a part of the view core team member and also the consortium gigs and that's pretty much it more focused on the typescript side of the view next currently it's your turn liam hi i'm liam debeezy i'm the lead developer on ionic view which is our ui toolkit for building cross-platform apps with you three i'm very excited to be here i'll pass it to luke next hello everyone my name is luke i'm from australia and i'm one of the quasar core team members and i'm mostly focused on um education so i do mostly education videos for quasar uh over to you carlo um paulo i refi a member of the quizar core team with mainly focusing on typescript support and now testing i also work on my own company 31k which do web app development and consultancies to fred i guess right is for beauty i wish i could see but i'm screen sharing uh looks like fred is disconnected okay well we'll come back to fred later on but exciting that he's working on astro um did we miss anybody anybody that's not on the slides that needs to introduce themselves okay yeah so quickly going over i just want to give you an all i i give the agenda apologies that it's only in one time zone um but uh basically this is the introduction and then well introduction was a little longer i think nothing expected but evan will be going into state of view next time we'll be having a great discussion about that also q a this is where you know again we've gathered a bunch of questions from the community but you know panels feel free to just like jump in have it be organic right we're all just having discussions here and um uh you know feedback is great then we'll have a quick bio break we'll do community updates as well where um there's a bunch of folks who have a lot of amazing updates about uh what's going on within the v community which is going to be awesome as well and then we'll just have an open-ended discussion as well uh just a quick reminder as well that there is a code of conduct that the view uh community abides by so please be nice to each other and um yeah i think with that evan i'll let you take it over all right thank you tracy uh so i'll be sharing my screen yep give me one second let me go ahead and let you do that okay go ahead all right so can everybody see the screen share now just want to make sure oh wait i'm not sharing my screen sorry i thought it's uh it's just this thing on your side okay here we go yeah okay okay cool uh hello everyone so um this will be a really quick update um so i will assume um most participants are kind of familiar with uh the you know the basic stuff so uh we'll mostly focus on what's being what's being new and some of the high level plans um things that we we think is important and or worth discussing so uh the latest update is obviously we released 3.2 back in august so uh not long ago and it turned out to be actually a much bigger release than i had planned uh so we shipped a ton of stuff um first of all script setup is out of experimental uh for users who use composition api in single file components this is a pretty big quality of life improvement um and it's been working pretty well so far um style v-buying also out of experimental this allows you to essentially bind a css property with a with a piece of state from your component reactively also with very minimal overhead and runtime so this is kind of just an improvement on top of the existing sfc style features we also ship define custom element allows you to essentially wrap any view component as a native custom element this has previously in view two we had this as a separate uh library but uh in v3 we just decided this is better shipped as part of the core and also this is because um since v3 uh has now tree shaking so if you don't use this feature it doesn't have as much impact on the bundle size of of your app right um so we are aware that there are a few uh cases that this api currently has issues with specific with css styling extraction so we're probably going to work on that before we go go on new features for 3.3 so this is something we're aware of and will be addressed and also some important reactivity performance improvements uh thanks to uh some really impressive pr's from the community um effects scope api that unlocks some more advanced reactivity patterns which is now already being used in view use and pinia um esm built an improved streaming api for the server renderer um so this is pretty cool in the sense that you can now easily bundle view server renderer for worker environments for example uh in cloudflare workers for edge rendering uh we also provided new streaming apis that allows you to essentially hook the rendering output to any kind of streams we also have high level wrappers for node streams and web streams so i'm pretty flexible now uh also a new directive called v memo this is really for advanced performance optimizations not really commonly needed but uh could be useful in cases where you are rendering a lot of rows in v4 uh this is the primary use case for it um and that is pretty much for 3.2 uh actually before we go into some of the new rfcs uh there is one small thing i kind of want to mention that we recently shipped in 3.2.13 so it was shipped in a patch because um it didn't really constitute any sort of api change but this is probably important for tooling authors to know that uh in after 3.2.13 we expose at view compiler sfc and apps view server renderer these two packages previously you need to install them separately when you have a view project that needs to compile single file components or do server side rendering after that version these two packages are now actually dependencies in the main view package and you can access them directly as just remove the act so now you can access them as directly as view slash compiler sfc or view server renderer now the benefit of this is first you just need to install one package there's no more need to manually keep all the packages in sync right because previously we require these patches to always have the same version but now since they're under the same package they're always the same version so if you work on a tooling that depends on these two packages um you can essentially uh and if you control the view version of you you're using you can essentially upgrade to a version beyond three point two point thirteen and you can now drop at view slash compiler sfc or add view renderer instead use the deep import from the main view package um so this is uh this only affects tooling authors but i think this is also a good uh improvement because it avoids the sort of version mismatch um that could potentially happen user land projects okay so um two important new rfcs that's still pending discussion one is the ref transform uh if you go to so the discussion uh is on in the vue.js rfc's repo discussion number 369 and uh the gist of it is um so this example kind of illustrates it uh we have a few new compiler compile-time macros um instead of using the import reference view you prepared it with a dollar sign and now this is a reactive variable it works like a normal variable except that it's reactive so if you assign it a new value it will just trigger updates um essentially the whole purpose of the rep transform is so that you can rely on reactivity without having to use dot value um so this would feel pretty smell like right and the online transform is also really straightforward so as you can see on the left is the code you write on the right we simply remove the dollar sign we will auto import the ref it's not already in the file and any access or mutation to the variable binding in the same scope you will see that it has a dollar appended and that's pretty much it uh this works in nested functions this works even outside of view components right the main benefit of it is it works outside of your components now uh some lower level details if you dive into the rfc um you will see this but uh it's really about how the concept came about the two uh the the whole transform is centered around two operations one is turning refs which are actual objects into reactive variables and the other one is turning them back into actual reps because sometimes you need the actual ref to be passed around into other functions or essentially when you pass them across function boundaries you need to convert them back into actual reps now so there are two operations and the dotted ref that we just saw is essentially a shorthand for dollar wrapping the ref so um here's an example of using the transform inside a composable so this is kind of the very standard example we always use to explain what a composable composition function is right you have a used mouse previously you would declare them as after wraps and you would have to use x dot value here now you can just assign them and so all the code so the only thing changes really you change this to use the dollar notation and now everything works like normal variables and the end of it when you return them wrap the returned object with the double dollar and it will just actually return the actual refs right because if you don't do this we are actually returning just two numbers but you want to return the actual rest to retain the reactivity but the nice thing is the only sort of the only change you are making is at the top where you declare these variables and at the bottom we return them so all the logic in the middle will be simplified now when you consume composables right so this would also work not just on these using the syntax right the usage here this will work on any kind of existing view use functions for example the dollar sign not just converts single reps to variables it also supports destructuring an object of refs into uh reactive variables so um when you use this syntax these are also a similar compilation these work like variables but are underlying their their actual refs so um as we can see here this transform is not view component specific so we can apply them to actually any kind of jsts files it would work everywhere um so that is the new rough transform so feedback is greatly appreciated and another thing is the props destructor transform uh the discretion is 394. um notice this uh i don't have a formal rfc for this feature yet so this is linked to a the actual proposal is down in the comment thread and we already have a pull request for that uh basically the idea is um well currently when we use props inside script setup you have to use define props right and one of the common gotchas in use reactivity system is you do not destructure the props right maybe you have been bitten by that if you destruct the props you lose the reactivity in order to retain the reactivity you have to always do props dot something otherwise it won't be tracked as reactive but with compile-time transforms we can actually support syntax like this that allows you to destructure this also covers default values so you don't need to use with defaults when using this syntax you can alias a prop to another local variable you can even do rest spread right all of this will be compiled into whatever that should work as expected and these destructured variables will actually also be reactive so for example if you use it inside watch effect this will be compiled into props dot foo after compilation um and similarly uh so this has the same character like say when you want to pass it into an external function you need to remember to uh sort of wrap it in a getter um so there will be some caveats to this this is why i also this is also why this is experimental right so uh we would like to see some feedback in the description thread as well uh but we believe this will be compare this to uh the syntax using with defaults we believe that uh this will be also a pretty good quality of life improvement okay so um the new documentation so as i have uh teased a few times on twitter uh i've we've been working really hard on the new docs so uh videos slashdots in the next branch so now this branch is heavily working progress so uh just um if you're looking at the the current code a lot of them is not updated yet so uh please do not send prs or suggest changes until we complete the whole uh revamp um there is a staging deployment so um i want to walk through some of the high level um hello things that we have been working on so this is a new page and uh first thing you notice is we have a dark mode now uh pretty sweet um the other thing is um we re-wrote completely rewrote the introduction um so we want to be we the first the main thing we noticed a few things we noticed is first our users previously our docs is focused on a no build tool experience you start with absolutely no no knowledge of build tools or single file components and we only introduced as kind of an advanced concept later but in reality we see that in reality our developers 90 developers on twitter responded there using single file components so this is actually the mainstream usage so you want to kind of adjust the documentation to reflect that right so in the new introduction you will be introduced to the high-level concept of what view does as a framework what is a single file component and the different api sounds right we have options apn composition api we also want to get this up front so that users know that um they are choices um we also added a new essentially we give you some upfront comparisons and explanations on which one you probably would want to go with and then we have a new faq we also try to offer different kind of learning paths for users with different preferences some users may prefer going with a tutorial so this is work in progress some users may prefer to read a book like format the guide which is very detailed very kind of slow paced covers everything summer users may just want to look at examples so the example section is completely reworked now we have a full reference that's working directly in your browser so uh every example you can edit them on the spot and what's cool is we also give you the toggles to switch between composition api and options api so every example is written in two api formats so you can toggle between them to see the difference understand how they work underneath and notice that every example uses the exact same template it's only the script part that changes for people who are not using single file components you can even see how the example would work without a build tool so this is literally the html you can copy paste into your browser to get it working without a build tool so we want to cater to because view is very flexible we want to cater to different use bases user bases people coming from different backgrounds with different use cases so we put a lot of effort into making sure so these uh making sure people can have read the documentation with the ideal set of apis and build environment that they're comfortable with right so these preferences will be persisted so if once you make the choice you can hide them in subsequent visits you always see the preferred api that you chose uh api index also kind of got a revamp we had now list everything here so you can filter them say i'm looking for watch so everything relevant to watch will be filtered here so you can quickly jump to the one that you're interested in um yeah so that's um that's the main use stuff in the in the docs um and some of the sections for example the reactivity part uh we have different content based on whether you are using options api or a composition api so um the whole learning flow the whole guide has essentially be half rewritten in a way that the flow is exactly the same as before but now you can actually go through the whole whole guide while focusing entirely on composition api um so you can choose to learn view through options api through composition api go using the same guide so because the shared concepts they share most of the concepts so the only thing that defers is how some of the api examples some of the code examples are different right so um hopefully this would help more users to be able to um essentially um reduce the sort of uh starting with options api then going to compensation api and sort of uh this learning process is kind of different right so we want to be new users should be able to just directly go with the api that they prefer um so that is the new documentation again it's very very work in progress so if you read it and find something weird uh we are we're still working on it um new default recommendations uh some of the tentative stuff in our new quick start guide we are moving from vci to create view which is a just essentially a very thin scaffolding layer on top of beat vcr is webpack based so we will be moving to beat for very obvious reasons we believe it's going to be the better choice for the majority of users especially new users so um some of the stuff that we want to improve in the new vase setup is mostly testing integration so that's a part where we would appreciate suggestions or feedback we're also going to recommend the new vs code extension volar over reader so leader has been doing a great job we really appreciate all the effort that went into it but um with more users going into typescript uh relying on script setup right uh vollar just provides a better integrated typescript experience and even for users without typescript [Music] and volar also kind of comes along with uh typescript focus tools like vue tsc that allows you to have the same diagnostics on the command line when you're building your project so um this is going to be a new default recommendation we're also considering what we should do regarding state management because vue x in its current shape is not typescript friendly and and especially with view 3's composition api usage it is actually becoming much easier to define your own reactive stores without the verbosity of ux so and then eduardo has also been work doing great work on pinia which is a more much simpler and more flexible way of defining stores with v3 and also already works with devtools and ssr so we're trying to essentially have a discussion around how we want to consolidate these and have a better default recommendation when you need state management across components so the two to three default version switch uh how we originally wanted to do it much earlier but obviously um we decided it's better to do it when we have the new docs ready because it's going to be a whole new set of base recommendations for new year's users to get into so when the new docks are ready we're going to do the switch everything will switch to v3 by default all the repos npm tags documentation so this is going to be a lot of logistics work so uh i expect this probably to be happening in november um or definitely before end of the year um famous last words uh 3.3 um so currently 3.3 uh the plan features we have a bunch of things in the backlog but the high level idea is 3.3 will be ssr focused um the the low hand fruit is uh hydration strategies for async components this is kind of partially inspired by astro right um when you so in v3 when you define an async component uh we can essentially give you a hydration strategy for example do not load your code even you're on the page do not load your code until you scroll into view do not load your code if you're on a mobile viewport right so these kind of hydration strategies can improve hydration performance and there are some other micro hydration payload improvements for example marking areas as server only so that it's only dynamic using dynamic data during the server rendering or during statistic generation but on the client it's considered a static node this is partially already kind of being experimented on in vpres so we want to kind of move these into a more generic api that you can leverage in more cases essentially but this involves a lot of fine details on how to make it safe and low mental overhead so there's a bunch of work that we need to do in that regard and then we want to finalize suspense in 3.3 and this will kind of rely on some feedback from the usage in nuxed and other frameworks so uh that is the high level gist of it i didn't really mention anything for the two point x line but uh just to make a note 2.7 still on the road map but given the current state of things we'll probably have to push it back a little bit but it's still something that we want to pay attention to all right so uh we're going to some questions yes so i'm checking both the the youtube channel and the question that were already sent by by people over in the last couple of weeks anyone on the call would like to ask any questions before we move forward so um uh as we know the view um the view 3.1 has been released with the migration build has been released a couple months ago so um even do you know um what has been that option of it how many people actually done the move over from the v2 to v3 uh so you know to actually use it if you had any chance to see the the move towards the v3 with that this is actually a very good question and to be honest i haven't been collecting enough data to know exactly how it's going so um any feedback would be really helpful in this regard actually if anyone actually has go through the process and run into issues but so far we have a few we have we have seen a few issues from people actually you know raising issues regarding the combat build uh in the vue next repo but i don't think there are issues that are very severely blocking obviously we're aware of it and we will probably continue to improve that and hopefully we can keep it around because so far it hasn't really created any sort of maintenance burdens on vuenex so i think we did a kind of a good job on how to architect it in a way that we don't we don't have to pay extra cost is keeping it around so um but we'll definitely make sure it can still continue to help people thank you so much um this is um another question that actually had from having a chat with people that actually using vue and they were trying to do the v3 is that some um i spoke with a couple of people that are flagging maintainers and they were you know they were talking about the struggle and a little bit of um uh extra extra push they need to do to maintain both view two and view three i know that this was touched lightly in the past is there anything any any tool or suggestion or anything that is coming next to actually support the the people's maintaining the two uh two main versions so my main recommendation would be to so so obviously we mentioned that 2.7 is going to back for the composition api so um and today with udemy you kind of already have that capability so my suggestion is try to extract the logic as much as possible using the standard set of composition apis which will work the same way between v2 and v3 and also already works the same way if you use vuedemi to sort of shift your library so um i believe most of uh a very large portion of the the logic that you need for kind of external libraries or even components can be extracted into this shareable logic um using composition api so it's um that's that's the the suggestion i can give right so essentially if you rely on very specific youtube behavior think about how maybe it can be refactored into uh into composition api style code that uses the universal api between v2 and v3 that would be the safest way to go amazing thank you um i also want to say something about that point um i hope that until the end of the year uh i can i can publish something on that topic but i'm currently exploring um a couple of a couple of things like um how do i put this my goal is to provide a couple of packages that are a combination of eslint rules that help you to like navigate the different apis what you can use in view three but not view two what you can use in youtube or w3 you have to like walk this narrow path like you don't you can't use a fragment and you also can't you always have to put uh have a root note in the transition group even though you don't need it in view three but you didn't you two so all of these things you have to essentially navigate when you want to write code or templates that can be compiled both for view 2 and q3 and so um if you are writing components i want to have like linear lint rule config which i also already have going i want to provide a small wrapper around define component around the defined component function that essentially can at runtime like translate the different lifecycle hooks which is like before created versus before unmounted uh and stuff like that and i also want to have written a small wrapper around the two different versions of the test utils so you can like mount the same view file with view two and view three and so all of this is still still in motion and i like a bit of time to to to work it all all out uh currently but i will hopefully have a little bit more time and and by the end of the month uh to work on this uh also work on a guide around this and the end goal is basically to have templates that you can clone from github uh with uh examples where you have basically a v3 package with components that you can build with reach of course and you have a second view two package which doesn't even doesn't really contain code it basically reuses the source of the v3 package but compiles it all for vue 2 with the appropriate packages that support it it's still very much a work in progress but i just want to tell the community that there is work going on and i also was in discussions with daniel a bit about this um we want to explore this uh this this road further and we want to provide additional tooling that will make it easier to write components in the future for these scenarios that's amazing thanks so much i think what you what you just mentioned the you know the templates and you know documentation that's precisely what have you know the main the question that probably would have would have you know the what was needed to answer those questions thank you so much and i'll keep an eye open for anything to be able to share it with the rest of the community as well thank you so much for that good good um let me check my questions um there's no question coming from from the community yet or from the chat that i can see and uh yeah you i had a couple of questions but you answered them all on the introduction uh so that was uh you know so as always you answer you answer them even before i ask them uh so that's a good thing and um well that's that's really mainly everything i have and i think the main question will be to see the the rest of the community and uh you know how things are coming across how how everyone is ready for the view through immigration and see if there is any uh you know we'll see with the rest of the rest of the tournament rest of the panelists as if there's anything like that yeah ahead sorry no i was just checking the internal chat as well this too many chats going on oh yeah that's funny yeah we do have still you know about uh 40-ish minutes on just kind of open discussion q a conversations so um panels feel free to open whatever discussions y'all want to have um and again you know for those of you watching on youtube feel free to ask questions and we'll go from there or evan do you have any questions you want to pose or feedback you were hoping to get well uh yeah i would i guess the the most interesting thing for me is the two new rfcs where people think of it um just general impressions and whether it's whether it's actually a good direction that we should go into because uh right because previously when we had the first draft of the ref transform it was very controversial so eventually we didn't really do it but this new version we feel much more comfortable because it's uh the scope is actually much well-defined and yeah and the the thing i didn't mention is because it's completely valid javascript syntax it works out of the box with any sort of tooling parser or typescript even we have full type inference for those macros as well so um yeah so curious to hear what people think on that and um i'm curious to think uh and another thing that could be interesting is our new default recommendations like going from ucli to create to create view a beat based a setup and yeah just uh make sure that the our contributors are also aware of the high level movement that we're going to make and make sure everyone is on board with the plan from the initial feedback that we had in the chat in the youtube chat it seems that people really um were really happy about both um uh you know both fcs that were uh mentioned uh and as a personal user as well of the view three i can say that i will surely be happy to use the ref transform i think it really improved the readability of the code um so and you know i explained in the dot view dot value to new people using it it's always been a bit of a extra thing so i think it will really really help for people to adopt it anyone else in the chat i don't know if it's completely relevant from uh the developer standpoint but i know that for at least working on beautify you know our representation of dot value has been a a way of being able to definitively tell that something is reactive within larger code bases so i i can say from that particular standpoint it's been very useful to us being able to quickly identify if a particular property is reactive without having to adjust its naming convention yep definitely uh one interesting thing that we do with the these reference forms is um when you the variables declared with the ref transform actually has a slightly different type so it's not a plain number type so when you hover over it you'll see that it's actually a like a ref value so you will know that it's actually a reactive value i was actually going to ask how typescript would work with those so it's not actually a normal number it will actually have a specific type that's fantastic so you can so in times square you can actually declare a type with like number and something right so we add a special marker on top of it make it a slightly different type that's actually compatible with numbers but still when you hover over it you see that oh it's actually a special number um [Music] i have another question if no one else says um it is about uh typescript so um i know that it wasn't mentioned to be optional i know that um you know it's you know it's shared across just it's nice to use it because it will help if you're creating a package and so forth um is there any typescript mentioned or covered within the view three documentation that your you guys are reputating yes absolutely so the whole new type secret session probably needs to rework uh we so uh the story with typescript from vue it's kind of a you know when we when we first uh introduced vue the original api options api design had no typescript in mind at all so thanks to the community they contributed very creative usage of typescript to make the type reference work for the options api but the type is very very complex it's kind of hacky and um and it breaks down in certain cases for example when you have uh when you have mixins or it just makes the type explosively more complex internally to maintain as well right so um so one of the main reasons we started looking for new api options in d3 was because of typescript and we explored class api in the beginning and notice that class api just it just can't have a good ergonomics without decorators uh but decorators as we have known has gone through some very unstable iterations uh as a proposal so we felt a bit risky to base a whole new api design on a proposal that may or may not change um and eventually that kind of let us down the composition api route and what we are happy about competition api is it works extremely well with typescript everything is designed to work with ts out of the box and actually it requires very little manual annotations so um that is the primary primary benefit it is like when you use typescript with capture api you don't feel that it's in your way most of the time you would actually feel it's helping you most of the time for example uh say you have a ref because of typescript you can confidently know it whether it should have a dot value or not right um and we want to carry this over to the ref transform as well which is why when we design these sort of new syntax we want to make sure that works hundred percent with typescript uh every operation even with the sugar syntax needs to be fully type safe so um and we want to yeah so so the main design philosophy for view with typescript is we want to make the experience of using view as close as possible when you you use view with or without typescript and we believe we've um competition guide competition api achieves that pretty well um because um because it rarely requires manual annotations so your code will look maybe eighty percent the same eighty to ninety percent the same uh when you're using competition api between typescript or javascript um and um i think this kind of creates um we also want to reduce the uh the onboarding burden for users to get you know get started with viewing typescript right so the new scaffolding will come with typescript option of the box volar we we are recommending volar now specifically because of the the better typescript support um so we want to make sure like when you go adopt view with typescript it's not going to be a huge jump like you're you're you're paying a lot of onboarding costs in order to get the return we want to make sure like you can actually have a quite easy time of just say okay i want to use typescript now i can do that with vue and it has all these added benefits with very little cost that i'm paying so we want to make that an easier trade-off for for our users i think that being said we are still like lacking a bit of documentation for certain aspects especially when it comes to the template because uh even when we publish the typescript support uh with the composition api with u3 initially we didn't really have much type support in the template especially not during compilation which changed with a script setup in in on the one hand and with view tsc on the on the other hand and so i i have been in contact with a couple of people who are saying hey it's great that i can now use vue tsc but all of us all of a sudden i get a lot of type problems that i didn't have before which is good because it's telling you hey you're probably having a problem in your template but so far we're not providing documentation that is leading users uh to solutions to these type issues aren't we supporting the typescript in the template and with the v we are we recording yeah so currently we can just already do something in regards to the uh yeah i i think a category of problems was kind of unrelated because um a certain aspect of the problem was some users were running some users running ts loader with view loader with webpack and tsloader will actually so when they use that setup ts loader will be type checking the compiled template which in some cases maybe uh we didn't do fully type you know the type may not just pass the check so it's kind of a it's kind of a weird situation because technically you don't really want to use the compile template to do type checking but i guess it's nice for us to still produce type correct code but what you really want to do is to essentially use vue tsc to do the type checking because that works at the more correct level of your code um this isn't really an issue when you use the vase setup because these build process don't actually do type checking on the compound code instead we do the separate type checking view with utsc on your source code which i think is the more correct way to do it um but obviously we need to document all of these in the new docs which is you know the type recession is going to be completely rewritten so in an introspect of the typescript currently so even though with the template is it might be compiled using with wall our wall already supports like a type checking on the template and for example annotating casting a variable to a specific type is very useful in the template and before it wasn't supported but now you should be able to do it um and in terms of the documentation i'm trying to um to improve the types of our current compo the correct component definition to simplify because the component contains a lot of generic types there that they're quite confusing and for us to annotate manually it's quite complex so i'm trying to simplify that and i will probably write a few um a few guidelines for more advanced typings to allow library vibrate developers to be able to extract types from uh from a view component and do so many things uh also working closely with the with volvo creator to improve the volvo types to make sure that the types are working correctly in the entire template so yeah so it's our typescript is ongoing um it's only going yeah that's i think it's a it's a yeah it's you know it's one of those open topic currently and uh and also you know i'll i'll share them a discussion that had with someone going and starting a project in v3 and what they said is we decided to use the option api because we also want to use typescript sorry not option the composition api because we use typescript so it seems like people are taking the choice because they think oh you know the title if you want to use that script is too hard in the in the option api and the moving so i don't know if this is going to be yeah i don't know possibly going forward i wouldn't say it's hard hard or anything it's just uh using competition api with typescript feels more natural because uh that's that's how type inferencing typescript are supposed to work right you have functions when you call the arguments you know uh that's the the most purest form of type inference that how typescript works whereas with options api we're kind of going all the other way around with a lot of extra hacks in order to give you semi-complete type inference on this right the biggest problem is really like this is two magical in options api there's so many stuff on it we have to like correctly merge everything from all the sources onto a single object it's a lot of i would say like typed in gymnastics that we do in the source code to make that happen amazing thank you uh it seems like there's a couple of questions from uh people within the chat anyone uh yeah i have a question about uh um class api uh i've seen there's it's been lagging behind like it seems pretty complete at least for what they need to do right now but it's still in beta phase so my question was about is there something missing can it be released as stable even if we know uh composition api is superior in photo types with inference so this is largely so v class api is largely maintained by kardashian so he hasn't been really active lately as far as i can tell so uh so it really depends on how far he wants to push the project um like you know from from the team's perspective you know because of our bandwidth we obviously don't want to essentially tell people hey there is yet another way for you to write view components uh so in the official documentation we'll probably no longer mention view class components anymore um [Music] essentially it's a it's still an option right but it's only for people who have really really strong preference for classes uh which we can understand but again uh our default recommendation will no longer include included thanks and it seems like there was another question about uh tests jonathan yeah yeah yeah yeah sorry sorry i mean i could i could ask the question is this more i see the questions yeah all right oh yeah i think it's better if we repeat it i guess yeah all right cool yeah um it's more about the migration from view cli to create view i i really enjoy creating the apps with beat the only difference is i usually have to go through the same testing setup in order to write like unit tests so i was just wondering if there's any recommendations that um the create view scaffolding will yeah so we tested a bunch of solutions uh so the challenge with uh testing for feeds is that um so just is one of the most popular unit testing solutions right the thing with jess is it runs completely inside node.js and this is already one of the reasons why we have a separate view jets transform which kind of replicates everything we do in view loader and the v plugging just because just has its own transform system so that it can completely run node and up until just 27 it doesn't even support async transforms so that's been a major block blocker for us to say having a really smooth integration with just 4v because um it just just wasn't designed to work with a native dev server like like v so what we've found to be working relatively well is cypress with its component test runner um and cypress is also rewriting a major part of that stuff with v3 so they're actively working on providing a good experience with a v based setup as well so um currently there are still minor issues that we are trying to sort out so there will be collaboration between veet and cypress to make sure cyprus is going to be a very solid solution if you need testing both unit testing and end-to-end testing for a v-based project so um so that will probably be the recommendation that's what we're probably going to do in create view actually uh how trunk is going to talk about that a little bit uh in in the community updates section but in general uh we think cypress is probably you know it covers both unit testing and twin testing so that's kind of uh the recommendation now there are other possible solutions like say uh running mocha with puppeteer there is a plugin called vit mocha puppeteer but um in the essence in order to fully leverage what veed does because v v does everything as a native server right as a server so um the most correct way to ensure your your test code goes to exactly the same transform that v does is to run the actual v server and load stuff over it so um which means it's better to start the vdef server then load your tests using veet that requires a real browser so which is why we need something like cypress or puppeteer or playwright and then we need to sort of plug those test results uh to report them on the command line if you don't need to report it on the command line you can actually already say have a separate page use the the browser build of mocha and then write your test right there uh it's actually a very low overhead setup you essentially when you're developing you just open a separate page with mocha actually running in the browser and every time you edit something it also refreshes and reruns which is actually pretty cool the only thing lacking is like it doesn't report to the command line so you can't kind of rely on it in ci so so that requires a little bit of extra setup thank you so much for the answer um any more within the any more questions anything else you want to ask i saw another one in the youtube chat um saying is there any good advice for more easily migrating to vola so i think some people are interested in how you get from um yeah from veto to vola i don't know if there's any specific migration really required because you just write standard view code and these extensions should give you good support uh i'm not sure if there's anything specific that is that you rely on leaders sorry if you're still using vue2 and you want to use vola um there's an option you can you can basically add to your ts config which will um enable vellus type support yeah volar actually also works for view two uh with some extra setup so um yeah honestly i don't know if there's any migration steps required to be honest it's uh really just disabling reader install volar and you're kind of good to go you have to delete the view sim file like which twitter recommended so there's a uh we declare star dot view modules in a sim file so we have to delete that file otherwise yeah that's the only thing that make it so for example quasar and beautify provide that component uh in volar you you need to describe as a as an interface which can be already provided by the by the libraries to affect the global components interface um yeah so that's basically the major difference that i see from volvo to um vitor okay yeah i think this could be solved probably on the library side as we migrate to more typescript based uh component definitions so that we don't have to have a custom format instead we just rely on standard typescript inference thank you again um another question is from liam jim go ahead yeah my question was is there a timeline on the view cli to create view migration or really anything devs need to do to prepare for that uh not really so create view is not going to be a sort of migration target for vuci essentially we don't recommend people who already run of ucli to switch because it's working well enough uh so creativeview is strictly for new projects it's not going to be a one-on-one replication of uci it's just going to be really like if you're starting a new project you should use this but if you have an existing very stable project onto cli they're the only reason for you to switch is it will probably be a lot faster but the thing is uh stability for your existing project is probably more important to uh than uh having a faster dev server so it's kind of a trade-off whether you are willing to go through this migration uh to to get faster dumpster but it's not a requirement like you don't have to migrate to veet in order for your projects to continue working it will always work thank you again for the answer um good just checking again the the youtube for some questions yeah i just wanted to add that you can totally try to switch to vid while still using visualize that's what we've done at my company and we like we use the the view slide freaking vid and it's been working pretty well for us so it's worth the try yeah so uh yeah so on the topic of this someone was asking whether we will be bringing you uh the the vci ui over two feet um but again i think it's probably better if it's uh shipped as a separate plugin instead of inside beat itself so yep sure oh you just casually said sure so people will be counting on it um yeah it would be probably a bit different because um [Music] actually just don't do it when you have time right yeah this is uh there's nothing you must do i can elaborate a little bit like um i'm still planning on modeling everything related to view ui towards guru js which is uh the project based on tory and not really specific to view sli so you'll be able to do the same things in that you do in view ui but also on other other type of projects like next on or vite of eight or things like that so so be a little bit different than writing and playing for it but pretty similar sounds good good indeed christmas present from people seems like um we you know we we we reached a uh end of questions or so it seems for the view part i know that we still got a big chunk of time now uh going into the individual contributors and individual updates and i know there will be lots of questions as um as the ecosystem is waiting for updates and things for all of you guys so yeah um but if there's any additional questions or evan you want us to listen any additional feedback we still have 10 minutes here oh if we don't have further questions we can have a longer break i guess yeah or maybe we can come back maybe we just move the schedule up by 10 minutes because i think uh the community updates will probably have a little bit more discussion so maybe we do a break and come back at the 50 mark and then i'll put up my slides for that and we'll see you all in about 10 minutes all right amazing and for those of you watching on the youtube i also posted evan's slides in the chat so feel free to hop on those i know there was definitely a bunch of requests asking for those i think everyone is just starting to come back so welcome back and yes sorry about my slides saying 11 50 p.m not am all right nice joke at kamal yes now we can view again um so i have a few updates uh that uh folks on um here said that they wanted to do but i wanted to make sure i didn't miss anybody so i have uh liam who's gonna talk about ionic view uh kazia who's gonna talk about view internationalization fred who will probably be joining us in just a little bit talking about astro he'll probably go last we'll have luke and paulo talking about quasar philip talking about view storefront and then i have daniel and john potentially talking about next in beautify is that all correct and and i would like to talk about create view okay great awesome um anybody else uh john maybe you're talking maybe i can quick update the field tools okay so let's do so uh i may talk about the the view to set up for the screen setup things and also the other device experience stuff uh i'm working on if if we got times limit uh we if if we gotta turn that okay great awesome yeah let's try to keep our updates to like you know just a few minutes no more than five hopefully two or three or so and then that'll definitely spark the conversation because the uh last sort of half hour of the conversation it's so crazy how fast these things go right but uh the last half hour will just be like open-ended discussions and conversations and again uh you know panelists feel free to ask each other questions and then of course um you know on youtube y'all have been pretty active and asking questions so thank you for doing that but feel free to post your questions there and we will try to get to all of them so i think let's just start off with uh how to train quickly and you can give us a quick update you're muted by the way okay let's be sure my screen yeah absolutely give me one second look can you okay perfect awesome can everyone see my screen now yes okay so this is the new create view project and that i just open source data today you can view on github.comcreateview and uh createviewproject is the next generation scaffolding tool for fuel projects you don't have to switch your vcr projects to create fuel yet because it's a completely new uh start from scratch project that is only suitable for new projects uh and we make this uh tour very very lean uh i'll show you in a second so uh the create field uh major version number is in sync with the field major so and now that v3 is under the next attack uh you need to use the create view net as next version uh and and you'll get the uh prompts now and you don't see the uh the progress are on downloading the package because it's very very small that i bundled every dependency into the uh single js file that you only need to download about 50 kilobytes of content uh to start and every option is obtained unlike a vcri that you will have bevel and esd inter by default so now i'll create a very simple project that i obtained every choice so now you can see the new project and uh let's open vs code to say it's structural oh some obvious code is not working okay so let's just use the tree tool to see its content and uh we only have the [Music] only they have the necessary files to start a new project that is the view config.js and the source folder and the entry by entry index.html uh nothing more uh one thing is that we have the new extension folder um at the bs code extension um file uh ways as now we started the start to recommend roller for vo3 development so it's included by default if you are bs coded uh you haven't installed the motor in your vs code it will prompt you and we only have uh three dependencies for the minimum setup now that the field compiler sfc is bundled into the view package so the installation dependency installation is super fast when you're not streaming it sure is faster than this yeah it's only around 50 packages so and we can see the project uh in 0.5 seconds and this is the new landing page of the project uh we get every useful link that you might need during the development in the landing page so you can check the documentation and the recommended tooling and the ecosystem packages and the community and you can spot fuel by becoming a sponsor that's for the minimum setup and we can't check the most advanced setup that includes every option and that is typescript.jsx view router ux and the surprise let me try again with yes codes oh no uh maybe quit your existing vs code window and try again like uh no it seems you have multiple vs code running oh yeah uh so in the tab script setup we have an additional tsconfig.json and the ink.js that includes the type definition for these specific types and the view stream in one file and most of the cypress thing is under the satellites folder so this is for e3 testing and we have a unit testing uh with with cypress component tests so and in this new setup uh instead of putting unity testing files under a separate test slash unit uh folder we think that it is better to have the test specs alongside the component themselves the tests for helloworld.new component is inside the underscore underscore tests file and it works exactly the syntax is exactly the same as the uh e3 testing files that we wrote before uh the vs code is still in taipeiros because we haven't studied dependencies i think it's it also should be very fast because uh there are only a few additional uh dependencies um yeah it looks slower than it should be because hunching is located in china so the resolving calls to the npm registry is much slower because i typically see this several hundred thing finishing under a second or so yeah yeah it's mostly slow in the resolving steps and note that uh we also included an alias setup in the beats.config.cs because i see many people asking how to set up aliases in feed so i just included this one uh we used to have this in previous versions of ucla and that's the project and it's also available instantly and we're running out of time because we're like 10 minutes now let's discuss the last picture that is uh cypress component testing uh we have every script that you might need for tests uh preview or build built cyprus component testing is super fast but the stop startup time may be somehow slow and in cyprus component testing you can have the component rendered and mounted into the viewport so it's it's a much better experience than just and the environment is exactly the same as the e3 testing so uh there should be less gauchos when you run the unity tests and that's it thank you you create your package awesome right amazing work uh again if you have any questions feel free to post them in chat and we will uh get to kind of the open discussion after this uh next up liam cool thank you uh yeah so there's been a lot of really cool stuff happening in ionic world for view developers um so first i'll talk about ionic view which is our ui toolkit for building cross-platform apps with u3 so we're working on ionic view version 6 which has new components like accordion breadcrumbs and a redesigned date component additionally it's been updated with the latest ios 15 designs and we added support for vee a few weeks ago which i'm very very happy to see that was a really popular feature request from our view community members uh so ionic view version six actually just entered release candidate this morning uh which just happened to line up with today which is really really fun um so we're really excited to see that get out the door so check out ionicframework.com for that next we have capacitor which is our cross-platform native runtime for web apps so think of it more as like a spiritual successor to cordova with performance and developer experience improvements and full progressive web app support um the capacitive team just released cap 3 capacitor 3 earlier this year with bundle size improvements an updated permissions api and a new run command for the cli this lets you run your app on a device without having to open xcode or android studio so if you're a web developer looking to make mobile or desktop apps with ionic view beautify quasar or anything else be sure to check out capacitorjs.com and finally we have some great improvements coming to stencyl our component compiler so stencil lets you create and ship reusable scalable components that run in every browser and work with any js framework including view so the stencil team has been hard at work on view support with tree shaking improvements and improved support for veet and view 3. you can find out more at stenciljs.com thank you thank you so much very exciting and again feel free to post questions and chat for liam okay uh next up we have kazia for view internationalization okay so i'd like to give you two updates on vue engineers quickly about uit buying latest stateable version is version 9.1.9 so of course this person is supported usually currently i'm working on bui version 9.2 that currently currently version is better in this version we can use the we can use just some new feature and we can get some improvement one of the most important features is type switch supporting this feature will be improved your international national developer experience considering in especially resource keys composition in visual studio code second updated information about view int migration recently [Music] i've released the view 19 bridge view int bridge supports some migration to version 9 from version 8. ui team bridge is back ported the uint composition api from version 9. you can use it so you can migrate the step-by-step migration to view three applications by using backboarded view int completion api in your view to applications i appreciate that you are having me give up opportunity in my updates for community thank you so much awesome thank you so much okay going down the list uh next up we have fred or astro hey hey hi y'all can hear me yeah um yeah i uh i have some stuff to talk about with astro so um evan mentioned there was some cool view 3.3 stuff coming down the pipe inspired by astr that's awesome to hear um for those who don't know astro is a way to do some really interesting stuff with partial hydration so partial hydration is this idea of instead of treating your entire website as a javascript application where you just kind of send the code down you render it on the server and you're building an application where the components are all nested your entire page is essentially owned by one root in one application going back to a more traditional model where your pages page and it's html by default but then you can inject these little islands of interactivity across your site so the majority of your content on like an e-commerce site or a blog is static it's words it's texts um it's able to send that just as the static html no javascript needed to go down the pipe to power that and then that like buy button which triggers some confetti or the header um an image carousel those are all interactive so they need that javascript so you're able to at a much more fine-grained level control how the page hydrates and how individual components hydrate so you have these islands of interactivity what we call island architecture where the result is that instead of having to send down a lot of javascript you actually just get to send out the bare minimum needed to render your site to hydrate the components as needed you can control different parts of the site so one thing might be very important you can load it with the rest of your site content on load something else maybe it's to the bottom of the page it's like a really expensive heavy thing you can actually put a visible detector on there so it'll basically only hydrate as the user scrolls down to it so if the user never sees it they never pay the cost they get a faster site so this is really fun it's really fun to work on because it's just a very different take on web development um we just actually yesterday at the jams.com won the ecosystem innovation award we're a fairly new project but really just making a big impact in terms of you know not just doing another one of those javascript apps not trying to um do another take on next or next but actually a different way to build your site and architect that site so we're really excited about it we think it's a great story for performance especially if you're building anything with mostly static content you can learn more at astro.build astro.build on twitter where we post a lot of cool stuff there's a great reply you can play with the doc site all that cool stuff please check it out and oh sorry the most important part it works with you so the nice thing about treating every island as component um we get to work with every framework so view react spell whatever you want to bring to the table you can actually mix and match up to you whether that's a good idea or a bad idea but obviously first class view support is very important to us it comes out of the box we love the view community and um yeah excited to talk more about it awesome thank you so much okay next up we have luke and paulo and i understand you also have slides slides are looking good although we can't hear you if you're talking still can't hear you if you're talking i couldn't find the unmute button once i'd started the slides all right sorry about that everyone don't worry all right i'm going to dive right into this there's a few bits and pieces so i'll just um sort of smash through all of this uh yeah so quasa's had a rebranding so we've gone from this old logo into a new more modern logo and with that we're going to be working on the landing page for quasar we're rebuilding that um to make it clearer what quasar does and what quasar is and we're also doing rebranding for basically the framework of the entire site like documentation and that's based on feedback that we got from a survey survey a few months ago just about how people use the docs um what stuff they're using the most and so we're kind of i'm revamping the docs based on that feedback and to the framework itself we have view three support and we have ever since q1 and we're even out of beta now so we are on view three um stable we have been for a little while which is really exciting raspbian did a ridiculous amount of work to get to make that happen sooner rather than later um so that means we get to use the cool stuff like script setup ref sugar um all of that's going to work out of the box with quasar vola support is getting really nice now especially over the past couple of days um so you're gonna get auto completion for things like props events components um and even slots coming soon which i didn't even know was possible uh so i'm ridiculously excited about that and these two blue ones here events and slots that's stuff that we actually couldn't do in the past which is now possible um using vola so really cool stuff uh i wanted to mention feed support this is in the work so it's not currently available in quasar um except for some prototypes that we've done and also some community efforts as well um moving on to app extensions for those of you that don't know app extensions are basically ways of extending quasi-cool and exciting ways so you can like um you know combine the components um getting create your own boot files stuff like that just so the community can easily sort of plug into quasar um and we've got a lot of core app extensions that are created by jeff and one of the most notable ones is qcalendar and this this um app extension is absolutely mind-blowing so definitely check it out at qcalendar.netlife.app um his documentation there is for the alpha version which is going to be out soon um and that will of course support quasar version 2 and also other app extensions like q media player and q markdown are stable and the others are slowly becoming um stable for quasar version two as well uh i wanted to quickly mention ssg with quasar um because you know such a hot topic at the moment this is actually possible right now with an app extension using quasar version two so freddy's created this app extension worked great for quasar version one and it's recently now supporting quasar version two which is freaking amazing to be able to do ssg with quasar um testing so this is mostly um calories effort here uh and the most notable ones in support for justin cypress our testing is currently in alpha but one thing i'm particularly excited about is um it looks like cypress component testing integration is going to be uh available when testing is released which is awesome because we get super fast tests and all the all the benefits of that um all right last but not least education if you go to quasarcast.com at the top of the page there we have a getting started guide for quasar and that is for quasar version two so if you want to learn quality version two if you haven't heard of it want to try out the framework definitely check out quasarcast.com scroll to the top of the page and um you can take a look at the getting started guide there everything on that site is currently free um there is going to be paid content down the line but that's probably not going to be for like another few months so definitely jump into quasicast.com if you like learning through videos um quasar news.com is a new site that um that was released about a month ago uh pretty bare at the moment we've only just started working on it but it's also gonna have a podcast which is coming soon and in fact these lives that i'm showing you right now will probably make a good um podcast episode so we'll be ready for the um the first podcast in the coming weeks uh and yeah that's just gonna be a place obviously where we can update people with news you'll be able to sign up to an email newsletter cool stuff like that and the last thing i wanted to mention is that i'm actually currently working on a 72 plus component series and this basically runs you through all 72 of quasars components it's going to be a paid course and all proceeds will go directly to help with the development of quasar um so if you want to jump on the mailing list for when that's released go to quasarcomponents.com and by the end of the year all of those videos are actually going to be available for free to the quasar community which basically means every single quasar component you can um you're going to have a video that you can look at to sort of teach you how to use that component um if you prefer to learn through videos rather than through um reading the docs so yeah that's my update for the quasar world awesome just just jumping in for a small correction the volar support will be in the next release of quizzer so in the i think two dot something uh since uh we said it was uh are already already ready is not it will be the next release awesome and uh next up we will move on to uh philip who will talk about vue storefront yeah hey hey uh let me quickly share my screen because i prepared two slides when you were all talking yes quick quick slides on the fly um but yeah this is like okay do you see a superman yes we do okay awesome okay so maybe let me first like introduce what we saw from this because i'm aware that maybe some people who don't know so basically our mission is simple we are creating high quality tools helping developers to build amazing ecommerce storefronts that will hopefully make everyone happy uh and you may know or not that less than a year ago i think like yeah exactly nine months ago we transformed from a small open source project to pretty well funded startup and there's almost 50 of us right now so it allowed us to go you know much further beyond just delivering the framework and tackle this problem from a much broader angle so right now like what we are trying to focus on and what we are building into the storefront is basically around three things one of them is data orchestration so in the e-commerce space it's very common that you're using tons of different uh software's like e-commerce cms oms much much more and it's hard to orchestrate them so we are creating a gateway uh that is allowing to do this it is already present i mean right now we can use it it's based on expert layers but we are also building uh a version of apollo graphql the second thing is you have orchestrated your data uh but then you have to build the frontend itself so we are delivering tools that are actually meant to help us so the user from two which is basically a framework uh to tackle this e-commerce logic storefront ui which is a design system and ui library we also have individual libraries for front-end caching and all the different things so any kind of challenge that you would face while building uh e-commerce front-ends we hope to have a tool for that and a new thing that we are working on right now is called user from platform and this could be treated as a hosting platform for this storefront but we want to go far beyond that we want to release the first version i think like in a few months and we will have data access for everyone uh but we want to go beyond that because on top of this hosting platform to add a very very uh advanced analytics they're actually telling you exactly where you're losing revenue uh and for the business side of things this is very useful information and on a very lower level uh so apart from what we are building uh in terms of products we're trying to focus on having the biggest possible presence on the market so we are trying to deliver our tools to all possible e-commerce platforms and right now we have integrity with commerce tools software shopify spriter and this month we actually announced prestashops free there's also no commerce there's sap that is being built and from quite some time we already have a magento integration uh if you don't see your e-commerce platform on this please don't worry we'll be adding them from time to time and also you can contribute you can you know just ping us and tell that you want to work on some specific integration and we will support you as much as we can with them that's it from our sites thank you awesome thank you and in the chat people are asking you to post uh actually sorry not you luke to post the last two links sorry going back one um so look if you send them to me uh in chat then i can post them unfortunately uh youtube has these uh restrictions on what links can be posted but yes thank you so much phillippe um okay next up daniel from next and again remember everyone uh if you have questions i see a bunch of people posting things so keep posting questions and we'll get to them in just a little bit [Music] so um we've been working hard at next so it's been it's been great fun in fact at the moment a few of the team are actually uh together um and it's been been really great to be able to to work the reason we're working so hard is because the next public beta release is next week october 12th it's in my diary and circled several times in red i don't know if that's true for anyone else and basically this is the opportunity when we'll be opening up visibility into what we've been working on for quite a while and to the source code um it's it's not by any means of course uh i promise that next next three is stable but it's a chance for the ecosystem to start working with us which is desperately something that we we absolutely are looking forward to so um i think one of the things that makes nuts so great is the fact that people have developed so many uh amazing integrations and plugins they have so many different use cases for knox uh and so it's uh it's a chance basically to kick the tires uh see what's working and what's working well and what we need to to improve to start of a journey and it's happening on the 12th um some of the cool things we've been working at include the creation of a cli so you can um nutsy in it a new project uh in a really fast way we've transitioned the entire next ecosystem to esm so everything including all of the internal modules are fully mjs that's been lots of fun and we've been finding lots of edge cases in lots of modules and things like that and hopefully solving them and there's lots of opportunities to do other things just earlier today i merged a pr to add web web assembly support to nux so lots of exciting things happening amazing thank you so much daniel also oh my gosh commitments so excited for you i always get nervous about committing um okay next up john from pewdiepie i should have raised my desk beforehand hello so um got a couple updates with uh beautify three and some information about where the team is at what we've been working on and some things that are coming up recently we put a lot of time into our our form components we have a completely brand new validation system uh that adds some new features and functionality such as asynchronous calls and and default rules oh sorry you just uh the voice cut out a little bit sorry oh no okay yeah it's back now um so yeah we've been working on a lot of updates to the forum system including uh more in tune for control in line being able to turn on or off all inputs we have new inline validation components so now you can create any uh you can validate any set of components or anything that you want to by wrapping components validation rapper anyways so we also have some uh some additional components that we've been getting into the system uh for uh selection controls uh check boxes and uh radio inputs kind of making sure that everything works very well together and in the process of implementing some of the final touches for components like autocomplete and select with new filtering functionality that we have so if you've worked with unified data tables you know we have the ability to perform different types of filtering methods on different columns of data we're bringing that out into its its own composable as a reusable composable and has definitely expanded the capabilities and and will make things like autocomplete a lot more usable for for individuals being able to control individual highlighting for matches found being able to filter on multiple columns and more components than just data table and we have a lot of new components that are coming in the next in the alpha we have uh some data table information coming in we have a new component for for nested functionality uh if you've ever worked with treeview we're kind of taking all the functionality from treeview and we're homogenizing it so that it can be reused for things like list making a lot of we've been really crunching a lot of the apis together and and creating even more baseline functionality components so that you know if anything that you're using within the framework is something that we've built on a lower a lower functionality piece so that you can rewrite it if you want to you could use our inputs or selection controls and in this case down the future nested inputs excuse me nested content like a tree view without needing to use our version if you don't want to we also have a lot of updates to the tooling around beautify 3. kale has been working really hard on we have a new fight plug-in and for anyone who has worked with customizing variables on beautify and version 2 you know that we transpile directly from node modules which allows us to to really uh tree shake efficiently however it can be a lot slower in cases and with the the new plug-in we have a couple different processes for how we excuse me in combination with the beautify loader we have some new processes that are going to be available to users to where you can designate that you want to be able to override all of the variables or only overwrite some so that for example if you're using a component in your library that is not having sas variables modified we don't really need to recompile the sas for it so now there'll be an auto-generated css file which makes this uh you know making any modifications in version three with sas or on the beautify object instant with the fight which is pretty awesome we also updated our our sas um interfacing from imports to to modules so that it is a little bit more intuitive to define and overwrite some of our built-in variables and we're also giving a lot of options for people to be able to modify aspects of the framework that had previously been closed off the ability to turn off all of our utility classes or the ability to turn off of the css reset color pack etc we have a lot of options that we're bringing for users to be able to you know continue to make uh changes to what um kind of this baseline white label set of components that we just put a default interface with that you can change very easily some of these uh or all of these new features in regards to the beautify loader uh with the vipe plug-in uh does support uh the you know modular sas variable declaration supports the different compile methods for how you can combine overwriting variables for all or just some it does it does work with vue cli however we have not put as much attention towards that aspect as we have fight i think evan pointed out earlier that fight is just a overall a a much more sol more scenario solution so we've definitely put a lot more focus on that it's also just a much greater development experience working with beautify especially if you've had a work with a large site where you have a lot of custom customizations we also have some the new version 3 docs coming up and by new i mean right now the version that is currently live that's serving as the the base for of our next development is a hacked version 2 version 3 culmination just so that we could get things to work and get it up and going however we have finally added the last few components that we needed in order to provide a somewhat decent document to your documentation experience with the new version so we will have a new fight ssr documentation version of running completely on version 3 very soon and yeah the last the last bit that we have kind of is already in the works and some of it's released is futify has presets to where you can easily install and get an application set up with some recommended default options that um that the team has has perfected over the years and one of the things that you can do with this with unified installer now is you can directly install the alpha using the alpha for fight or the alpha for ucli and we have a couple different ways that you can do that now and the tooling that's coming out for those presets are because right now we have uh we have the concept of smaller subsets of predefined functionality for version two but it all hasn't been converted for version three yet right now we only have the single templates for either a vipe or ucl installation but we are bringing over um all these pre-configured systems to make sure that uh with version three you'll be able to quickly get a completely scaffolded project up and going very quickly and yeah so that's kind of what the team has been working on we we have lots more exciting things that we're working on in addition to this year and uh looking forward to putting out some additional information thank you for the time awesome thank you okay next up we have uh jonathan all right uh can you hear me yes all right i'm just gonna i also whipped up a couple of slides in the last couple of minutes i'm just gonna share my screen okay there we go [Music] all right uh can you see my screen yes we can okay i'll go back to the first slide uh yeah so with chakra ui uh we've been working a lot i think under the radar haven't had very much time to post the law online but uh this is what we've been doing so uh we've been working hard on the v1 release so far and some alpha release is already out not all the components already but people already using it in production and this is an example enterprise application that heavily relies on the theme api um and this is kind of the syntax that it allows you to extend the theme with and we can now define the component styles one of the the the features i've been getting from uh users is would like to like be able to define their components designed for in another document and not necessarily do it in a new component and then re-import that component and so with the new extent theme api you can be able to do that within your theme object you can also define custom variants as well and these variants can then be responsive to your to your components we also were able to due to some help from the community some people have actually uh managed to backport the theme for the theme api for v1 partially into v all point x so if you're using 0.10.2 onwards 0.10 and onwards you can actually use this this feature directly inside of your your components we also added a mode utility that simplifies how users can you can toggle between values depending on the color mode um so instead of importing the component this was actually a tweet done by one of our team members instead of having to import and inject the current color mod into your component context um you can directly access it using this the global property that we provide using cold mode and it also works not only within the view view context it also works in your regular javascript file so if you ever need to to access this value in case you change your color mode in another javascript file you can access that and it will work just fine [Music] we also are working on started doing some early development on version two and this has actually kind of been i feel guilty because it's distracted me a lot um the idea is we're trying to extract the logic between uh between the the logic that we are duplicating between view and react for those of us that know check our ui access both for vm react so we decided to use state machines and then write view composition api hooks to consume the state machine and then pass the state onto the components so this allows us to split the ui components into logic and just ui so we have two types of kind of machines we have ui machines for for state and and logic and we have other machines for just design and i think this is interesting so community members are interested in in helping us crank this out this will be good so if someone wants to rock on like chakra smelt uh it'll be a lot easier you don't have to rewrite all the code and then we're also working on a chakra ui extract which will allow us to walk through your single file uh components and and extract all these styles out and so you can have a zero runtime styling api for those that are interested in this it will also work in in react as well and uh this is a this is also very early development so the repository is not public but i think it's interesting for for it's i thought it would be something to share so in case there's anybody interested in contributing to exist uh we're active on our discord so please feel free to reach out to us and that's it on updates from chapter ui thank you so much and last but not least we have anthony giving updates so yeah so like yeah so like things like everybody is announcing like new cool new things so uh i also i also heard that a lot of people are still stuck on views too so like due to like i i support or some like code codebase migration thing so uh so i'd like to mention a few tools to like uh help you back to like uh enhance your view to app so uh can you kill c my screen yes we can okay yeah so like the first uh the first well known one is like the view composition api which we back for the uh our competition api back to uh from view story back to view two so like you can use the uh composibilities like uh like original like it's really hard in some of the really hard options api i'm one of the maintainers of these plugins and then i think this plugin is quite stable now and i think many of them are using it so uh the other one is that sorry i mean okay okay uh so the other one is that i originally made for like youtube story setup so like street uh screw setup is kind of a new new crew things of a new sexy things like we can have in the view single file components to like make our code most uh simpler so so like while this is original like view three only like for now like we we can bring back to like view to it so like what's mentioning is that this plugin is like called unplugging which is powered by uh which is made by like next lab so you can see that in the in our install guidance like you can you can use like almost any tools like you are using like for example like webpack or a view cell i like also nox so even with vola like you can you can have like even uh knocks three like typescript support uh for view uh for this uh scripts for the squares that i think has and also like red sugar so uh this used the exact package from the next uh from view three that view through exporting uh the ref transform logic uh under the at view slash rav transform package so like we we are using them so like you can actually get the exactly the same behavior at the view three so while this is experimental when this syntax is out of experimentals we are also aligning with the user changes so so then we can like push unplugging ecosystem even further so like we have the file system components auto importing things with these plugins and also uh unplugging uh auto import like for you you can even get rid of the riff and the computer input like it will be accessible globally and then like you can use them as you want so uh to sum up like we can combining all of this together and then like this is an example like uh for nuts too which is running on that phone is running on youtube so uh as you can see like i i can't open up a small demo here so you you can you can get the the first class type lang ts file for sql setup and like you can get all the typescript uh support and like for example like i can i can make a double called computer you can see that we have the we have all the all the compression for these apis and then like for example here so if we change the ref to screen like you can see we got the type arrow like you cannot modify a string a string on that so we also get a [Music] bit uh on top of mac 2 so like you can you can have the uh instance um hot module reload um on max so this is basically it and also like in the upcoming uh next three days we are also like a release next bridge that's bring uh bring back the next three uh functionalities or like cool new things to uh not too so like you can you can start using uh not serious uh features now like and then like migrate to nuxter later so and that's that's all for me for uh for this touring thank you so much yeah i'm always so impressed you know all the different javascript communities are formed differently and they have like different ways of doing things but i'm always so impressed with like how much is going into the view community and how many people have like adjacent projects uh you don't see that as intensely in some of the other communities so it's really great and uh i love that so uh going into just kind of the next 20 minutes of just having conversations i know there have been some questions and everything like that and somebody uh we'll take it over amazing thank you so much tracy it's it is great uh to do this these events because we can hear so much progress and how much work goes behind each release and everything else and anthony you are it's amazing how much you can provide to the community so it's you know i'm a i'm a view user then everything every now and then i can see your you know your new things there's great fantastic work from your side and fantasy work from everyone so you know everyone is great um so um again you know there are some questions in the youtube chat also question internally if you guys want to ask um there was uh one question in um in the youtube chat was about um someone tried to use astral insecure to use astro uh with script setup and they went into some issues so uh fred any do you know if there's a fix coming through or are you aware or how is that going yeah i think i'm aware of that issue and i think someone there might even be a pr for that um yeah i i actually haven't gone into it myself so i can't really speak too much detail but first class view support is very important so anything like that is treated as a pretty high priority bug um we also internally just moved from snowpack to v which is you know evan's project so there's some great view support out of that where snowpacks you support was always a little you know can't compete with evan building you know so much great view stuff so we definitely want to invest in our view support and uh moving to vita is definitely one step towards that direction as well amazing thank you so much for the answer um also you know some of you covered it during your discussion your introduction some of you did not so um which one are our old projects now supporting you three uh so i didn't manage to get this few if you uh store front actually support v3 i know that with beautify is coming so you know if anyone can just chip in and say if support is coming if there is any timeline because i know that that's what's stopping some people to upgrading or actually taking you through this new project so yeah i can maybe speak about this storefront and basically we are based on max so as soon as next we release the public beta we'll try to align with that uh we already have written everything in the composition api so the transition should be simple of course like i i don't know how many breaking changes are in inaudible but like the restore from itself i like we're doing as much as we can to have a very smooth transition for our customers and people from the community thank you so much anyone else you say this as soon as you get released we know precisely that it's the 12th of october midnight or one o'clock what uh that would be uh that would be a dangerous thing to promise i'm joking sorry you don't have to say the time zone and that's it that you're saved let me see um um i wanted to ask questions on but i can see that even it's gone so let me see oh yeah quasar shirts was mentioned what about all the beautiful shirts why they were mentioning the chat what what did you hide first uh yeah this is this is something we're currently working on um with niccolo who's the um uh quasar's designer uh yeah so we've already like done a few test shirts we just want to make sure that we've got something that's super comfortable um which takes time because then you've got to wait like two weeks for it to ship and all that kind of stuff so we are still working on that um and there will be quasar shirts i'm predicting probably within the next um couple of months um but as we seem to have established um setting hard dates can be dangerous amazing i'll send you my size i'll tell you so we can get that sorted okay um and um when i may say the chakra again i may say the name wrong to apologize about the introduction was mentioned that um the components were split between the logical part and the designs part so um how did that decision come across and and what can you say about that because it's something very interesting on actually doing it and how do you find that um yeah i think this the the the decision for this came about because um the the chakra ui it works this works beyond just vue.js it works also for react and if we found that like for each version um we had a lot of code duplication for example like you know the effects and maybe some of the state and i'd have to redo that in vue.js as well and if someone were to come along and they wanted to do build like another version of that in in in felt that would result in a lot of duplication of time and so and so we decided to for v2 um this might be the biggest change uh just extracting them so using state machines because we found these to be the a common paradigm that would allow us to support this without doing too much gymnastics and then within the framework uh context we would then use composables and this is where react and view i think are are very helpful so of course the state machines will need to have some reactivity so for that we we thought about using view reactivity but it's we found that its bundle size was a little bit larger than the we used a voltaire for as as the alternative and um but but so far everything is okay we wrote a small a smaller state machine uh compared to uh x-state uh for for this and um yeah so far that was the main reason i think i probably overanswered the question now that's perfect thank you that was a great explanation i think maya you may you have a question for us no i sure actually um when i heard about when i heard that jonathan tome said about using x day or stay machine in chakra i was very very excited because i'm a fan of appstage so i wanted to ask him about how did he find the writing about state machine huh how does it change the way he developed the component library for compared to before and that and i understand that it's not using app state right just build your own x-state machine on based on the cons sorry beyond the same machine based on the concept of xa isn't it right okay yeah um i think i'll answer probably a last question first the the the the public api for the state machine is actually the same as as x-state so you could take your state machine and put it into the x-state visualizer and it would still show the maps uh for it uh i wish i had slides to show um but um it that that it does work uh the same way the public api is the same as far as writing components is concerned we are heavily relying on um on on when we define the the the state or the context for the state machine we then destructure it for the components that are supposed to consume that state and so on the browser side we on on the when you import the component we will then use the mounted hook to then initiate the state machine uh depending on the type of component that it is especially for accessibility heavy components and we found that it's been a bit more robust so now we can write a single suite of tests for the state machine and we're sure that it works whether you put it in view and react so this is this is i think how it's changed we are we haven't used it in production yet but i think the react team is planning to release a range slider component in v1 uh so this one relies on the ui machine so i think you could also look at that okay cool that's very cool thanks that's fantastic thank you so much i think there's a person that everyone would want to hear about is the view dev tools we haven't had any update yet about that so have you got anything to other tell us for that yeah yeah maybe maybe you can do do you hear me well yes maybe i can share my screen yeah switch to my computer um okay is it is it good yes yes indeed great um so i recently shipped a few updates to the view devtools i don't know if um everybody knows but there is a new website delegated to the devtools you can go to and there's a guide um and picking development oh maybe it's broken okay yeah something something going on here so there's a there's a part of the documentation website dedicated to uh plugins which is a very um exciting new uh feature in the devtools i think i think i think that's the most exciting video for me um because it basically means that um any um third body beginning in the view ecosystem can hook into the devtools and add new the beginning informations and basically improve your the beginning experience and i think i'm not sure that's already been done before but you can you can go to documentation here and there's a whole guide on about how to use the devtool api and for example here we can we can see in the pinea demo from eduardo that pina is actually adding new features directly into the view devtools using the devtools pubic api so we can see in this component that pina is putting some specif special states um in addition to the default default ones here you can also see that we have a new an entire new inspector provided by pioneer so we can browse the opinion state here um and recently i made some updates to devtools so here's the latest version um running on on the development channel at their own application here so you can see that now the devtools is going to show a little navigation if your viewer version is out of date and the most exciting thing about those recent updates are that plugins got even more powerful because we can now can now like control the permissions of the plugins so for example if you don't want to see the events on the timeline from this particular pregnant or you know the the additional component data you can toggle this off and the plugin can even add settings custom settings to further like improve and customize the beginning experience so here we can see that this um this plugin is like providing us with a few settings here so it's like basically you say oh i i can like uh i want to display a toggle or a choice or text input and it's going to display here in the chrome devtool button panel amazing so that's it for my good update that's fantastic great great updates and uh um i'm loving you know i love the new changes in the update in the last version so we'll learn that um i think next up is ben ben we got something to tell us yeah hey everyone um so i imagine you know with all of us being in the pandemic um you know we are getting used to these remote events but also as a result one of the benefits of this is that there are a lot of speaking opportunities when it comes to remote events especially when it comes to meetups and that kind of thing so if you've always been ever been interested as far as like organizing sort of communities um you know around you or whatnot or want to get started with public speaking this is actually a really great time to just sort of gain that experience in the meantime so if you have any questions feel free to reach out and happy to help facilitate that um because we always love seeing new speakers and hearing about all the amazing work that everyone is doing so thanks mom thanks much thank you for that is yeah i i'm really hoping can come to view london so remote event on our back come on guys back to face to face um i think a little updates that i personally am interested in other people are it's probably some more a couple of words on beat if you can even if there is anything you can see on you know what has been released recently anything else coming up uh yeah so uh we just recently released v 2.6 uh honestly i've been mostly focusing on the view docs side but the v team is doing great work uh i did add one uh performance improvement in 2.6 so 2.6 now defaults to es failed for minification we actually had to essentially like raise the feature request to es bill so that it can properly do tree shaking when minifying a single file so that was resolved in the latest version that you guys built i actually made a had to learn go to make a pr to to but i mean the pr didn't get merged but anyway we got what we want so uh now beats can use the s build for notification by default so uh which is like 20 times faster so uh default builds will be a lot faster and then we also shift another performance improvement that uh essentially when you hit the first request to the server you will start to eagerly pre-transform uh every direct import of that module so that um [Music] so that we can start transforming them before the browser even send the http request right because uh if we only transform on demand then we have to wait for the back and forth between the browser and the server uh for everything to be transformed but we can actually eagerly sort of like a pre-warming right anthony has actually worked on something like that as a plugin but now we have it built in so uh all of you users will enjoy it out of the box so this mostly helps when you have a lot of modules that need to be loaded in parallel um on the first mode right so on subsequent mode it's mostly the same and then for uh further updates so once i finish the docs i think one thing we want to finalize in lead is to rework the ssr dependency handling issue so there are a bunch of dependencies that have problems when you try to use an ssr so we want to resolve that properly uh probably gonna require some reworking of how we handle the dependencies overall uh but that is probably the major thing left for us to tackle um some other smaller things like um we probably want oh another thing we want to fix is um when you have say raws view or spell files in the dependency um you probably want to properly apply yes uh the the actual transforms on them when we're building with uh pre-bundling them with this build currently there's a bug when you uh when your view files have like say relative imports it creates duplicated modules it's a kind of a complicated problem but it's something we also intend to fix um and finally there's uh some small things like uh support native import maps that's actually a thing i just noticed that uh we currently uh doesn't respect native import maps uh so this is a nice thing to have because supposedly we want veed to any valid any any code that is valid in native uh should be valid in via uh in vt as well so that's one thing we need to fix anything thanks so much for the updates um you know i was surprised when you when you pushed them when you tweeted about now wave t is even faster than before because of course you were super fast you were how could it be even faster so that's great uh very very ugly to hear that um we do have just three minutes left uh any um any hot topics or things that you guys want to discuss so the one question i probably have is um i have not personally used pina yet and i know that it's a kind of starting to people to discuss a bit more and so uh as any of you use it in production or is everything you're thinking about uh migrating ux to uh to pina and what is the taking i know that he was discussing some of the slides and some of the people so okay go ahead yeah i'd i'd love to share on this i think um i was really surprised that um how simple pina is i think it's it's very easy to think of a library um like a state machine and think oh i'm going to get a whole bunch of basically crap that goes with it but pena is really really straightforward and if you can use vue then you can use pina it's just a really nice way to break up your state we're actually using it with vuex as well at the same time simply because it was a better alternative for us than just using the composition api to manage states so yeah i think people should definitely go ahead and give it a cr give it a try and they'll be surprised at just how much benefit you can get very quickly with pena yeah so from from our perspective um one of the major drawbacks of the current view x4 api in terms uh when we use with view 3 is first of all it doesn't have proper typescript support so a lot of the areas for typescript is is missing in vx mostly especially when you're dispatching actions like which are string based like it just doesn't have the full type coverage right so uh another thing is when you say want to do state management when you do a lot of state management or when you write a lot of composables and composition api code 3x just feels you know stuck in a different paradigm so this is why in some cases some users just use a single reactive object as a store right but then a single reactive object has the problem of uh not working with dev tools it makes it a bit too free-form right uh so pena is kind of like in the middle where you still have um have some sort of convention it works with dev tools it works with ssr it's really well thought out right most of the problems you'd have to solve with the state management system it kind of deals with those problems but at the same time stays simple and out of your way so um this is something we are really considering to sort of uh in fact like uh if you look at the define store api uh of pina we've been having an rfc about vue x like what the next version of ux is like and it turned out to be very different from vx4 and more like penis so pd is kind of like what we wanted to do in the rfc so um this is something we i want to talk with eduardo who is unfortunately not here today so we want to go over this and um see maybe we will probably recommend peony overview x especially for view through users especially if you need typescript right um and um and there's also a possibility for us to even have it built in right like import define store from view wouldn't wouldn't sounds pretty good to me right so uh there are a lot of possibilities so we can uh we'll probably go over this uh with the team uh just to make sure we're on the same page but i like you know personally if i need a state management system i like today with view three with typescript i would definitely pick pina overview x4 that's amazing and if you do it even i think 99 percent of the people without let's say 90 let's do this but amazing so um uh looking forward to hear that probably you know to see probably more information on the twitter feeds and information shared by the community uh the time is actually up so we have completed this fantastic event it's been great to hear all the different things people are very excited about everything all the new things that the chat that that we discuss on both in twitter and on youtube so um i'll pass the mic to 3c to do the closing notebook thank you so much for the fantastic event and discussion with yeah thank you so much evan do you have anything to say before we say bye um not much uh thanks everyone for attending and uh really appreciate uh it's really exciting to be able to you know because we haven't had real conferences for so long it's uh and even for online conferences we mostly just give the talk and don't get a chance for speakers or team members to hang out together like this so i think this is great and thanks for everyone uh thanks for all the updates great stuff and hopefully we'll see the ecosystem so after the dock switch i i'm hoping really the dock switch will uh the new docks will help just push the whole ecosystem start to massively adopt v3 so thanks yes thank you so much thank you everybody all these folks are typically on twitter so if you go to viewmeetup.com you'll actually see everyone's twitter handles and everything like that you can follow along after that and you know we hope to continue the conversation on twitter on github uh so and on discord so see you then and thanks everyone for joining see you bye

Channel: This Dot Media

Views: 1,668

Keywords:

Id: gpTbH469Qog

Length: 152min 21sec (9141 seconds)

Published: Thu Oct 07 2021