- 24
- 28 560
Vue Germany
Germany
Приєднався 28 чер 2021
Deine deutsche VueJS Community. Hier findest du Videos rund um Meetups, Tutorials und Technik.
Impressions of VueJS.DE Conference 2022 - The VueJS Conference Germany Berlin
For the community, by the community
conf.vuejs.de
VueJS.DE is the first community-driven Vue conference in Germany. It has taken place in Berlin, 05. October 2022. The venue BOLLE FESTSÄLE is located next to the beautiful Spree river, close to Bellevue palace and Tiergarten. A bunch of one-day workshops happened on October 4th.
It was a wonderful event and we hope to see you again next year.
0:00 Antony Konstantinidis; Organizer VueJS.DE Conf
0:26 Eduardo San Morote; Vue.js
0:40 Natalia Tepluhina; Vue.js core team
0:55 Isreal Ortuño; VueJobs
1:17 Daniel Roe; Nuxt
1:30 Franzisca Henke; sum.cumo Sapiens GmbH
conf.vuejs.de
VueJS.DE is the first community-driven Vue conference in Germany. It has taken place in Berlin, 05. October 2022. The venue BOLLE FESTSÄLE is located next to the beautiful Spree river, close to Bellevue palace and Tiergarten. A bunch of one-day workshops happened on October 4th.
It was a wonderful event and we hope to see you again next year.
0:00 Antony Konstantinidis; Organizer VueJS.DE Conf
0:26 Eduardo San Morote; Vue.js
0:40 Natalia Tepluhina; Vue.js core team
0:55 Isreal Ortuño; VueJobs
1:17 Daniel Roe; Nuxt
1:30 Franzisca Henke; sum.cumo Sapiens GmbH
Переглядів: 424
Відео
Alexander Lichter: unjs - Unified JavaScript solutions - vuejs.de Conf 2022
Переглядів 1,2 тис.Рік тому
🎤 Speaker: Alexander Lichter 📗 Description: JavaScript can run almost anywhere nowadays - in the browser, on the server, in lambdas, and on the edge. And so do our Vue and Nuxt applications! Talking about Nuxt - Already when developing Nuxt2, the goal was to keep the core lean and release additional functionalities as Nuxt modules, or as separate packages. This decouples the functionalities and...
Jakub Andrzejewski: Fast & Headless → Build Headless Commerce in minutes - vuejs.de Conf 2022
Переглядів 485Рік тому
🎤 Speaker: Jakub Andrzejewski 📗 Description: Building Headless Commerce from scratch seems to be very difficult. But what if we could instead use best of breed tools like Vue Storefront, Shopify and Storyblok to build our Headless Commerce in few minutes rather that weeks/months of development? This is fast! In this presentation, I will guide you through the process of creating Headless Commerc...
Daniel Kelly: How to Migrate from Vue CLI to Vite - vuejs.de Conf 2022
Переглядів 2,3 тис.Рік тому
🎤 Speaker: Daniel Kelly 📗 Description: Vite has revolutionized the Vue.js development experience with its lightning fast server starts and HMR. It is the definite first pick for starting up any new project. But what about your existing projects that use Vue CLI? Vue CLI projects can be migrated to use Vite to capitalize on that awesome developer experience. Learn the steps to get it done! 👉 Mor...
Daniel Roe: Building for the Edge with Nuxt 3 (live coding) - vuejs.de Conf 2022
Переглядів 9 тис.Рік тому
🎤 Speaker: Daniel Roe 📗 Description: We'll take a tour of Nuxt 3, creating, building and deploying a real, live-coded app to a serverless environment. We'll talk about how changing requirements in today's serverless world require frameworks to change, and how that makes a difference for UX and performance. Along the way, we'll also explore how Nuxt 3 makes developer life easier, some cool new f...
Markus Oberlehner: Vitest or Cypress? Why not both?! - vuejs.de Conf 2022
Переглядів 1,6 тис.Рік тому
🎤 Speaker: Markus Oberlehner 📗 Description: The general wisdom is to use Cypress for E2E and Jest/Vitest for Unit and Component Tests. But nowadays, Cypress can also do Component Testing, and we can use Vitest (with Playwright) for E2E testing. So how do we decide which tool we should use? Or should we use separate tools for different kinds of tests? And how can we use those tools to write good...
Thorsten Lünborg: The right perspective for working with script-setup - vuejs.de Conf 2022
Переглядів 759Рік тому
🎤 Speaker: Thorsten Lünborg 📗 Description: Vue 3 introduced the Composition API and with it, the 'script setup' style of writing your code blocks. Now, with Vue 2.7, all of this new goodness is also available in your current Vue-2-based projects. Reason enough to do a proper deep dive into this feature. In this talk you will learn about the inspiration and motivation for this new style of writi...
Marc Backes: Building Vue 3 On Stage - vuejs.de Conf 2022
Переглядів 609Рік тому
Marc Backes: Building Vue 3 On Stage - vuejs.de Conf 2022
Debbie O'Brien: Testing Web Applications with Playwright - vuejs.de Conf 2022
Переглядів 1,3 тис.Рік тому
Debbie O'Brien: Testing Web Applications with Playwright - vuejs.de Conf 2022
Natalia Tepluhina: Spin the wheel: building a truly reusable composable - vuejs.de Conf 2022
Переглядів 1,4 тис.Рік тому
Natalia Tepluhina: Spin the wheel: building a truly reusable composable - vuejs.de Conf 2022
Eduardo San Martin Morote: Stop writing your own routes - vuejs.de Conf 2022
Переглядів 1,2 тис.Рік тому
Eduardo San Martin Morote: Stop writing your own routes - vuejs.de Conf 2022
Live Q&A Panel with Evan You - vuejs.de Conf 2022
Переглядів 2,3 тис.Рік тому
Live Q&A Panel with Evan You - vuejs.de Conf 2022
Opening & Warm Welcome - vuejs.de Conf 2022
Переглядів 172Рік тому
Opening & Warm Welcome - vuejs.de Conf 2022
Introduction to vuejs.de Conf 2022 5th October, Berlin
Переглядів 5332 роки тому
Introduction to vuejs.de Conf 2022 5th October, Berlin
VUE.ing Playgrounds with AWS Amplify - Vue.js Frankfurt meetup
Переглядів 1602 роки тому
VUE.ing Playgrounds with AWS Amplify - Vue.js Frankfurt meetup
Using Astro.build - Vue.js Frankfurt meetup
Переглядів 3,1 тис.3 роки тому
Using Astro.build - Vue.js Frankfurt meetup
Looking forward to meet the community again.
so where did he mention "edge"?
yeah, of course, it is so easy to migrate)) anyway, thanks for this helpful video)
Cypress also has Component Testing, anyone with some opinion on this?
Skip to 19:43. The TLDR is if you want fast tests but no ability to see why it failed, use Vitest. If you change a component and quicker iteration feedback use Vitest. If you want play by play of everything that was tested use Cypress. IMO it's not really worth it but its cool that you can do it. Downsides of using two testing frameworks: * Code duplication sort of * It is a blackbox * This technique of using two testing frameworks can be bad if you write a bad test in one and write a good test in another causing confusion if the code is bad or the test is bad. * Extensive time, training, and knowledge is needed to write in both frameworks
Great content
Silk smooth dude! 🙂
Is there a place where we can see the source code? Doing the same as in the video but I'm facing some errors that don't seem to appear during the conf live coding. -
the big problem we faced while working with "setup" are 2 typescript limitations: unubility to use external interfaces for properties, not possible to infer component types from outside
I believe they fixed all these in 3.3 update
How to Migrate from Vue CLI to Vite - but why?
how he use http comman in terminal like this? is this node packge or what?
You have a amazing personality!! Increase your stats = Promo`SM !
🎉🎉🎉🎉🎉🎉
🎉🎉🎉
When can we test vapour?
Hi Markus, great video! The only issue I have is I can not use the VS Code Vitest extension to run/debug the tests when using the bridge solution. How do you manage to debug your tests? Thank you!
Thanks! True, that's a drawback of this solution that I encountered too. However, the unsatisfying answer is that I never was a Jest/Vitest/Playwright VS Code extension heavy user, to begin with, but mostly use iTerm 2 to run the tests (in watch mode). So I don't really miss the feature and therefore didn't think about a solution. Maybe there is one, but it's also possible that this is a trade-off you must live with if you decide to go the Bridge Driver route.
To be honest, I don't see the point in using this composable because it doesn't reduce much of the code.
I think composable making the code reusable, so you can use the same code wherever you need, it's the same idea as DRY (Don't Repeat Yourself). Definitely not reducing the code.
Creating loading, error, result variables in every call is exhausting for my soul 😂, thats why composables come in handy.
This is a great talk! Thank you! I've been wanting to do my next project in Nuxt. This has tipped me over! Also. What is the terminal you are using? It looks very interesting.
Sorry but is not pretty abstract and not a truly reusable... sorry
Daniel, what is that window where you are making the requests. Is the a vieja-De prompt
Great introduction to the vue/nuxti-verse and very well explained too
badly explained the rectivity somehow, the docs in vue 3 reactivity in dept is better
Greate conf, i really like the host she seems not be there just to animate but she is in the business of javascript .
Awesome presentation! Codegen is amazing - really speeds things up to start.
thanks Daniel! You make it look so easy, you're a star 🌟
Can someone give me a TLDR of the whole video and explain why we need type checking in routes?
Yeah, I need the same thing. Someone?
@@theantibeta nicer tooling warnings? I have no idea.
Why would you not want that? You never refactored routes? Plus, the tldr of the video is that you should not be manually registering routes, you should use a generator which can do a lot more for you
Any questions left? Drop them by here 😋 PS: There were *some* breaking changes compared to the examples and the current 1.x release for e.g. h3.
Great talk! A question not directly related to your talk. Since you already have a YT channel, great presentational skills and have many contributions to Nuxt, UnJS, etc... Do you think it's time to start doing videos or general content creations?
@@_the_one_1 Thanks a lot 😊 Yes, this is planned for next year indeed 👀
It happened 😁@@_the_one_1
Awesome talk!
Amazing talk. Thank you Daniel
What a great talk. Thanks 👍
At 44:21, I found using `const { title, time, description } = Astro.props;` works in place of using `let` statements - which seem to render as null with Astro 0.20.12
With Astro 0.20.12, adding `export` to variables within the frontmatter will result in an error.
this is amazing
Nice video👌👌