search

tatethurston / nextjs-routes

Type safe routing for Next.js
MIT License
571 stars 23 forks source link

V1 #44

Closed tatethurston closed 1 year ago

tatethurston commented 2 years ago

Now that the API has begun to stabilize, we should consider what (if anything) should be added before releasing a v1. That release will mark the adoption of semantic versioning, to make it easier for users to reason about updates.

tatethurston commented 2 years ago

39 could be a consideration, though that will likely only be additive, and could be 1.1.

A solution for #36 would be nice to consider, though that is also likely to only be additive and I haven’t thought of a solution that doesn’t involve a runtime. That may ultimately be out of scope for this library and better served by something like trpc, because typed paths still doesn’t give you type safety for the request and response bodies.

alexgorbatchev commented 1 year ago

If the API is stable, just release 1.0. If there are changes, release 2.0 :) Personally I really dislike when packages stay in 0.x for years, while being used in production just the same :)

tatethurston commented 1 year ago

Agreed