Комментарии:
Because the samosa crack has been removed from the v vase which previously was a real bowl wine glass
Now the router bit can etch anything on any flat piece of wood 😂
vue-router/auto give me an error
ОтветитьJust use N....
ОтветитьAnyone else getting Cannot find module 'vue-router/auto'
ОтветитьAlways a banger as usual, thank you learnvue for the info.
ОтветитьThis looks amazing BUT use special characters on filenames is not good idea in my opinion.
ОтветитьDynamic import seems like a better solution. I've never been a fan file base routing
ОтветитьI can definitely see this devolving into an unmaintainable shit show.
ОтветитьNo, thanks.... don't think is an advancement.
ОтветитьHow do you use the same component for different routes? Wrappers?
Ответить⚠️ This package is still experimental.
ОтветитьIf you really hate someone, teach them to recognize bad kerning
ОтветитьSuch a great addition! Soo good to see you back making videos again too.
ОтветитьThis is awesome! Hey what IDE are you using?
ОтветитьWTH I am never leaving the vue space.
ОтветитьWhat is your editor theme?
ОтветитьFinally! Thank you for posting, i was missing your videos
ОтветитьCan you tell my if I can use this plug-in without typescript? I just started coding about 4 monts ago, front-end developer course, and I used vue router for the first time with my latest project. I don't use ts but can I still ues the new router plug-in? I think my last comment disappeared
ОтветитьI don't know.
This looks quite nice if you have some simple routes.
But I kinda can't imagine using this on complex routes with params and meta on large projects.
I would maybe prefer the other way around an IDE add-on that generates a nice overview from a route file.
Anyway thanks for the video.
the trade-off would be when writing guard, auth related, defining meta. because the route attribute (meta, name, etc.) is all over the place instead of in 1 file.
ОтветитьThe syntax in file name scares me. Honestly I would personally prefer the traditional vue routing approach
ОтветитьAlready mentioned that Nuxt is probably the best way to go, but if you are "stuck" with Vue only, this is a great tool. Maybe I missed it in the video, but it's important to not that unplugin-vue-router is developed by Eduardo (posva), the same person who is the creator of vue-router
ОтветитьThis is really really great , useful , thank you for sharing it and thank you for your great video/content
ОтветитьYour videos are always amazing, short, concise and full of practical knowledge
ОтветитьWe get rid of file based routing circa 2006.... please don't bring that shit back!
ОтветитьHonestly, even for single page apps I use Nuxt now. You can setup Nuxt to statically generate your app with the `ssr: false` property, and using `nuxt generate` instead of `nuxt build`.
The plugin system, autoimports, etc, are all achievable with different Vue plugins, but it's just so nice that it just works out of the box with Nuxt.
My one and only Vue content creator. My feed is usually packed with React. Which is kinda sad because I don't even know React.
Ответитьhow about layouts ?
Ответитьnuxt who?
ОтветитьWhat i love about current usage is using the name of the route so i don't Care what's the URL is
ОтветитьFile based routing is NOT always the appropriate answer.
For more complex apps with reusable components and tabbed architectures, you likely still want whatever.routes.ts files. Being able to just pass metadata helps. It avoids writing wrapper components around a reusable component.
Ty for the video! Very good news!
ОтветитьIs it possible to have typesafety with routes but still use router.ts, I don't like file based router, it quickly becomes a mess with lot of routes, your editor is full of opened "index.<insertSuffixHere>", and it makes translations of routes basically impossible 😐
ОтветитьYeeehaaaa :D :D :D
ОтветитьInteresting. the cons of this approach might developer need to learn how file based config works even they don't need SSR.
ОтветитьOne thing I don't understand, what does Nuxt do that Vue + Vite cannot? What's the point with Nuxt? Is it the bleedinge-edge version of Vue where they add all the good features there?
ОтветитьI was just working with Vue app that used router when you released this video. Immediately switched to unplugin-vue-router and it works perfectly. Switch was painless.
ОтветитьWow, this is INSANE. I always use Nuxt for the file based routing, but I got a new job and they are using Vue for CSR, so this is the perfect solution.
Hat off to the developers and thanks for the content
i use Ziggy because fullstack 😭
ОтветитьThanks for your videos!
I want to switch to TypeScript in Vue, but I don't feel comfortable yet. From what I've seen, there are multiple ways to write some TS features in Vue. In addition, the Vue team is also updating some TS features this year. That's why I'm not sure which TS features are best practice. I guess some are still in beta or might get optimized in the next months.
A video would be awesome about how to properly use TypeScript in Vue (with props, emits, computed, watch, ..., all the important stuff).
yes but nuxt....
ОтветитьCool. But I‘ll stick to vite-plugin-pages. See no big reason to switch now..
Ответить