Live data from Hacker News

Next.js 7

nextjs.org

11–20 of 40 posts

Re: Next.js 7

#11
post #2

Not clear to me from the release notes if there now is an easy way to proxy to a server in development (if you for instance have a Django driven API on port 8000). This is easily done with create-react-app by just adding a line in package.json. In Next you've had to either set up and configure nginx locally or proxia via an Express server, both options that that are a bit of a hassle to set up for such a common case.

create-react-app is actually removing this feature in an upcoming release. We don't have plans to include it as a feature to Next.js as you can already implement it using a custom server. We do have an example for it: https://github.com/zeit/next.js/tree/canary/examples/with-cu...

Re: Next.js 7

#12
post #3

Time and time again, the Next.js (and Zeit) team blow me away. The rate at which they release new, high-quality versions of their products is astounding, especially given how few people are working on this full time -- it's basically just Tim Neutkens, who's insane: he's constantly pushing updates, reviewing PRs, and finds time to be very active on the support channel. We use a bunch of Zeit's tools (particularly Nex…

> it's basically just Tim Neutkens, who's insane

Insane is an understatement. The dude has helped me on the support channel more times than I can count. Forever grateful.

Not to mention pkg is pretty awesome too from Zeit

Re: Next.js 7

#13
post #5
post #4

Earlier quoted context omitted.

> it's basically just Tim Neutkens, who's insane when looking at tools to build a business on, that can be a liability no?

Fair, but my confidence in it stems from the giant community around Next.js. Zeit, a company with a good reputation among developers, works on it full time. It has contributions from other big-name OSS contributors and big companies (Netflix, Hulu, Nike, Ticketmaster, Jet, Auth0, Marvel, etc.). It's definitely a liability if it were truly just one individual developing it, but I suppose it's more that there's a small…

As said elsewhere, I mostly act as a curator of a very large effort of hundreds of individuals. The project was actually co-created by several other people who work on infrastructure at ZEIT (e.g..: Naoyuki Kanezawa led all the initial releases, designed important parts of the framework, Arunoda Susiripala contributed the test harness and key build pipeline infrastructure, and so on).

Re: Next.js 7

#14

Which backend solution that isn't a service/CMS, but is more streamlined than Express or Koa would you recommend for solo devs going with Next.js? Is there something like a preferred full stack solution involving next.js on the frontend?

Next.js is not prescriptive about your backend stack, it gives you a way to fetch data using `getInitialProps`. At ZEIT most of our APIs are built using Micro: github.com/zeit/micro, which is a very lightweight way to build APIs.

Re: Next.js 7

#15
Could anyone explain what Next.js is? I use React (using create-react-app), but I'm under impression that React is a JavaScript framework (like Spring is Java framework, or RoR is Ruby framework).

So Next.js is a framework for a framework?

Re: Next.js 7

#16

Could anyone explain what Next.js is? I use React (using create-react-app), but I'm under impression that React is a JavaScript framework (like Spring is Java framework, or RoR is Ruby framework). So Next.js is a framework for a framework?

> Next.js is a minimalistic framework for server-rendered React applications.

https://github.com/zeit/next.js/

So a specialized framework based on another framework

Re: Next.js 7

#17

Could anyone explain what Next.js is? I use React (using create-react-app), but I'm under impression that React is a JavaScript framework (like Spring is Java framework, or RoR is Ruby framework). So Next.js is a framework for a framework?

React provides a way to build pages and components, Next.js provides the other pieces that make up a full-stack framework like routing, asset mgmt, and most importantly, server-side rendering. Getting SSR to work seamlessly with Webpack, Babel, and any other frontend tooling is a pain in the ass, Next.js makes it dead simple.

Re: Next.js 7

#18

Could anyone explain what Next.js is? I use React (using create-react-app), but I'm under impression that React is a JavaScript framework (like Spring is Java framework, or RoR is Ruby framework). So Next.js is a framework for a framework?

React is nostly the view layer. Next provides everything else.

Re: Next.js 7

#19

What's the closest framework for Vue.js and how close is it in terms of functionality? Asking because Next.js has been one of the reasons I've become more interested in the React ecosystem.

As others have mentioned, Nuxt.js is what you’re looking for. And, it’s pretty great to work with. Prior to using it, I just got “done” building out my significant project with vue, just plain vue. When I started this next one, I decided to give Nuxt a shot, and it has been like the missing piece I was looking for in the previous app.

It provides structure to you app, gives you everything you need to build out a front end out of the box (router, vuex, build system, etc). And deploying it is a breeze, giving you the option for static html builds, or a SPA, or you can go full blown SSR, with the best part being you can switch between them whenever seamlessly if your needs change. It provides enough opinion that your project has a consistent structure, but doesn’t get in the way if you need to so,etching outside of norm, extending and configuring it is a breeze. And to top it off, the docs are great.

Definitely would recommend it to anyone looking to build any sort of non trivial front end with Vue. I know my next few projects will certainly be using it.

Re: Next.js 7

#20
post #19

What's the closest framework for Vue.js and how close is it in terms of functionality? Asking because Next.js has been one of the reasons I've become more interested in the React ecosystem.

As others have mentioned, Nuxt.js is what you’re looking for. And, it’s pretty great to work with. Prior to using it, I just got “done” building out my significant project with vue, just plain vue. When I started this next one, I decided to give Nuxt a shot, and it has been like the missing piece I was looking for in the previous app. It provides structure to you app, gives you everything you need to build out a fron…

Thanks for sharing your experiences, could you recommend any resources for plugging data into Nuxt? This is what I've always been curious about coming from Meteor
Post reply on HN