Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Nuxt.js over Vue.js: when should you use it and why

bornfight.com

Post reply on HN
Print view View original

31–40 of 80 posts

Re: Nuxt.js over Vue.js: when should you use it and why

#31

Post by ehutch79 »

There are people over on reddit who say that EVERY project should use nuxt. from the lowly todo app, to huge erp projects...

Yet, especially for ERP projects, most of those features are problematic. Like SEO. I don't want a search engine to ever see my content. In fact, my robots.txt says not to index it. SSR is a non starter, since everything would vary based on the user, we're just shifting the rendering back to the server, for no real gain other than the round trips on the api. The routes can be a problem as well. My routes have different navigation guards depending on permissions and state for the user, i haven't checked but i doubt auto generated guards based on folder structure wouldn't handle our weird business logic. COmbined with the difficulty of dealing with errors server side, nuxt.js isn't going to work in these kinds of cases.

TL;DR Nuxt.js does not work for everyone, even if people say it does.

Re: Nuxt.js over Vue.js: when should you use it and why

#32

Post by brianwawok »

nullpilot wrote: post #23
brianwawok wrote: post #11

So the point is to improve SEO of Vue apps Perhaps useful to some sites. Assuming Google has issues with Vue. Not useful for someone doing content behind a sign-in that isn’t going to ever be SEOed anyway?

I've found the dev experience with nuxt to be more enjoyable overall than it is with vue-cli. The main reason for that I would say is that you don't have to bother with routes and the generator can set up Tailwind (or other CSS frameworks/tools) Generally, it feels like it strikes a good balance between being fully configurable boilerplate and opinionated framework.

Ah. I have Vue with DRF, so I can already skip routes if I don’t need them.

I don’t send JS, my CDN does, so not a big win there.

Re: Nuxt.js over Vue.js: when should you use it and why

#33

Post by psychometry »

brianwawok wrote: post #11

So the point is to improve SEO of Vue apps Perhaps useful to some sites. Assuming Google has issues with Vue. Not useful for someone doing content behind a sign-in that isn’t going to ever be SEOed anyway?

That's just one point. Nuxt is the best way to built a multi-page web app with Vue components. Once you're using vue-router and Vuex, you might as well use Nuxt.

Re: Nuxt.js over Vue.js: when should you use it and why

#34

Post by iratewizard »

swyx wrote: post #14
taywrobel wrote: post #8

Earlier quoted context omitted.

Sort of makes me bummed out that the Dart project failed. If there was one time when we could have escaped the client side hell that is JavaScript it would have been then, when chrome had astonishing market share, and Dart could compile down to JS to ease the transition until native support became standardized. But nope, here we are with anotherone.js every week.

what makes you say it failed? Flutter is growing strong.

It's ambitions and potential versus its current adoption make it a relative flop. Plus, since it's made by Google it may randomly end up in the graveyard without warning.

Re: Nuxt.js over Vue.js: when should you use it and why

#35

Post by thomasedwards »

We use Nuxt on a fairly large project. One of the biggest problems we’re having is that there’s no routes file you define yourself, you structure it by putting views in folders. This is a nightmare once you have more than a few models. It also leads to highly confusing page names, and if you have more than one variable in a route, completely screws everything up. We’ve ended up grouping things together in folders just to make it easier to manage, but that directly effects the URL.

Re: Nuxt.js over Vue.js: when should you use it and why

#36

Post by whoisjuan »

In my humble opinion, you lose a lot when you go fully static. One particular case that becomes a pain in the ass is redirections. Nuxt has some redirect modules but they feel super half baked.

Also routing is a mess. Really no way to set up routing in a decent, understandable way.

So in my opinion just use Nuxt when you are sure your website is not going to need any complex functionality that is easily achievable with a server middleware. Pretty sure that there are other ways to achieve good SEO and in general Search Engine indexation without giving up so much.

Re: Nuxt.js over Vue.js: when should you use it and why

#37

Post by avolcano »

thomasedwards wrote: post #35

We use Nuxt on a fairly large project. One of the biggest problems we’re having is that there’s no routes file you define yourself, you structure it by putting views in folders. This is a nightmare once you have more than a few models. It also leads to highly confusing page names, and if you have more than one variable in a route, completely screws everything up. We’ve ended up grouping things together in folders jus…

Does extendRoutes (https://nuxtjs.org/api/configuration-router#extendroutes) not work for y'all? I haven't had to use it (yet) but I was happy to see an escape hatch, though I could imagine it not scaling very well...

Re: Nuxt.js over Vue.js: when should you use it and why

#38

Post by jmkni »

whoisjuan wrote: post #36

In my humble opinion, you lose a lot when you go fully static. One particular case that becomes a pain in the ass is redirections. Nuxt has some redirect modules but they feel super half baked. Also routing is a mess. Really no way to set up routing in a decent, understandable way. So in my opinion just use Nuxt when you are sure your website is not going to need any complex functionality that is easily achievable wi…

I feel as though if you just want a static website, you're better to use one of the more mature frameworks designed for that purpose, like Ruby on Rails or Asp.net Core etc.

I worked on a project built with Nuxt about a about a year ago and I really didn't like it. Everything felt like a chore.

Re: Nuxt.js over Vue.js: when should you use it and why

#40

Post by jimbob45 »

whoisjuan wrote: post #36

In my humble opinion, you lose a lot when you go fully static. One particular case that becomes a pain in the ass is redirections. Nuxt has some redirect modules but they feel super half baked. Also routing is a mess. Really no way to set up routing in a decent, understandable way. So in my opinion just use Nuxt when you are sure your website is not going to need any complex functionality that is easily achievable wi…

Yeah this seems close to the philosophy of no side effects for functional languages. It's neat and has some nifty benefits for your code but for the 1% of situations where you need side effects/client-side rendering, you're gonna end up fighting the tool rather than enjoying it.
Post reply on HN