Earlier quoted context omitted.
Is this Now only as I'm sure most of us don't use Now?
Yeah Now only
Thanks but no thanks!
Next.js 8 released
111–118 of 118 posts
Re: Next.js 8 released
#112Earlier quoted context omitted.
As you probably know, Nuxt.js uses a folder to url mapping, so say /src/views/contact/index.vue maps to /contact In my case I wanted to be able to change the url depending on the language of the user. And not by prefixing it with a /en/contact vs /de/kontact. To make matters more complicated, I serve multiple domains from the same node/express instance and determine the correct site data to render based on the domain…
You can use custom routing and its actually recommended for bigger projects you can check it here if you want https://vuejsdevelopers.com/2018/07/16/7-tips-large-nuxt-app...
Thanks for the link. Good to see this is much easier now.
Re: Next.js 8 released
#113Next.js is an awesome framework, but dynamic routing is still a mess, and clean URL masking [0] is unnecessary complicated: you have to add a route handler to Express.js, and you have to use 2 different props to your components to make it work. The Next team explains it because they don't want to solve this problem by shipping a definition of all the route of the app [1] because it does not scale. But while it is tru…
We are using `next-routes` and they are working really well for us.
next-routes is good, but it was unmaintained for a long time, with issues and PRs (27 at the time of writing!) piling up. A new maintainer was just added [1] who seems more active, so hopefully things will improve.
[1] https://github.com/fridays/next-routes/issues/244#issuecomme...
Re: Next.js 8 released
#114What I don't get: Either you go full SPA or SSR. And If you go for latter then you can choose any stack, e.g. Rails, express with pug, Django, PHP, etc. Why do people take React's constraints to the backend? No bashing, really wondering what's so much better then. I know why a React SPA can be better than a SSR. But what is better about a React SSR vs the typical SSR?
> And If you go for latter then you can choose any stack, e.g. Rails
You suggested Rails, but a big reason people like Next is exactly because it's an opinionated, batteries-included framework like Rails.
The "vendor lock-in" situation, which seems to be one of your main arguments, is exactly the same time. If you don't like vendor lock-in, I don't know why you'd propose Rails.
Re: Next.js 8 released
#115Earlier quoted context omitted.
This is great comment and while Zeit/Next.js related folks are happy to explain in this thread why Next is so great, they're not give us any reason why we need to login for a random tutorial. Maybe it's to generate leads? Leads which can be converted to paying customers? This why this whole thing shouldn't be on HN, this thing is conflicted from the ground and driven by commercial interests.
Yo, you wanna chillout with flinging the accusations? Every single one of your comments in this whole thread is either bullheaded negative or a subtle suggestion that Next.js is some marketing conspiracy without its own merit. If you don't like Next or don't see its usefulness thats fine, but 30,000 stars on Github and pretty varied list[1] of companies seems to suggest that some people do find it useful. I am not af…
[deleted]
Re: Next.js 8 released
#116Earlier quoted context omitted.
I'm behind a mobile connection which has been acting up today. For me the experience on the website was pretty bad, as there were no loading indicators. I clicked on a link and it did nothing for several seconds. Since it's not a real page load, my browser did not show any indication of loading either. I'm not entirely sure what next.js does, but I would be wary of using this library due to the bad website experience…
Loading indicators are left up for developers to add in next.js, but aren't very difficult to do. I've used react-redux-loading-bar[1] in a recent small project of mine and it worked quite well so far. I'm not sure about working with the native loading indicators though. In general I quite like the way next.js is handling these things: It's pretty bare-bone but provides a lot of examples of how to do more advanced th…
Great explanation @mAritz!
Thank you for your feedback @Ndymium, we've shipped a new version of the website that has a loading indication (based on the with-loading example posted above)
Re: Next.js 8 released
#117Earlier quoted context omitted.
We're currently working on rewriting /learn to not require any login while still retaining the gamification element (in offline storage). Meaning that you get the best of both worlds. Just to explain the reason there is a login at all, this is mostly for historical reasons. The original learnnextjs.com built by Arunoda was based on another project he created for teaching Meteor. Anyway as said we're rewriting /learn,…
Very cool! Makes sense that you got it for free from Meteor, great that you're iterating based on feedback.
> great that you're iterating based on feedback
Thank you for providing feedback in a friendly way, we're always happy to improve where possible! In case you're curious we have a WIP pull-request: https://github.com/zeit/next-site/pull/159
Re: Next.js 8 released
#118Earlier quoted context omitted.
We are using `next-routes` and they are working really well for us.
next-routes is good, but it was unmaintained for a long time, with issues and PRs (27 at the time of writing!) piling up. A new maintainer was just added [1] who seems more active, so hopefully things will improve. [1] https://github.com/fridays/next-routes/issues/244#issuecomme...
Almost all of them are just version bumps. We wasn't needed anything for a year of usage.