News for hackers. Stuff that matters.

A comment on Next.js 3.0 Preview: Static Exports and Dynamic Imports. Parent comment

Re:Next.js 3.0 Preview: Static Exports and Dynamic Imports by fooey on Monday May 15, 2017 @05:47PM (#14345437)
I tried to do a project with next.js but their router was just too awkward and limiting. Unless you're doing straight 1:1 route to code, you're basically on your own.

https://github.com/zeit/next.js#custom-server-and-routing

[ Parent | on HN ]
Re:Next.js 3.0 Preview: Static Exports and Dynamic Imports by Rauchg on Monday May 15, 2017 @06:29PM (#14345731)
That's the opposite of what that page is trying to explain. We'll take a look at the wording in case it's confusing.

tl;DR: You can do any sort of routing! We use a /:org/:project scheme similar to GitHub at https://zeit.co :)

Some examples:

- https://github.com/zeit/next.js/tree/master/examples/paramet...

- https://github.com/zeit/next.js/tree/master/examples/with-ne...

- https://github.com/zeit/next.js/tree/master/examples/with-pr...

[ Parent | on HN ]
Re:Next.js 3.0 Preview: Static Exports and Dynamic Imports by fooey on Monday May 15, 2017 @06:46PM (#14345856)
The named routes example is probably pretty close to what I was looking for. Oh well, maybe next time.
[ Parent | on HN ]
Re:Next.js 3.0 Preview: Static Exports and Dynamic Imports by atrilumen on Monday May 15, 2017 @09:37PM (#14346758)
Does next-routes work in a static build?
[ Parent | on HN ]