@tannerlinsley
is there a built in for that in v1?

or I would have to declare 2 two routes, one with the param and one without it?

const route1  = new Route({
   path: 'user',
   ...
})

const route1  = new Route({
   path: 'user/$userID',
   ...
})

@tannerlinsley Is there a plan to make this more ergonomic? Something similar to react-router https://reactrouter.com/en/main/route/route#optional-segments?

It's really annoying at the moment to support that exact pattern from the react-router link above, that is to have a lang param that sits at the root of your routes.

/:lang?/some/really/long/path

You can declare two different routes, one for / and one for /lang - but that means you'd have to duplicate every other route that comes afterwards, which is very cumbersome (duplicate objects with different parent route if code base, otherwise duplicate files if the route is file-based).

An alternative is to redirect on "/" to "/en" (if you're doing i18n), similarly to tanstack.com:

https://tanstack.com/router/ -> redirects to https://tanstack.com/router/latest - works ✅
https://tanstack.com/router/v1 - works ✅

That would work really nice for the docs as well

https://tanstack.com/router/latest/docs/latest/framework/react/overview - works ✅
https://tanstack.com/router/v1/docs/latest/framework/react/overview - works ✅

https://tanstack.com/router/docs/framework/react/overview - doesn't work ❌

Our team is considering migrating from React Router to TanStack router, but this is the only blocker.

We have these paths

/skill
and
/skill/$skillId

We want to render the SkillPage component for two cases and type-safely use the parameters inside

const skillId = useParams({
  from: `skill/$skillId`,
  select: (params) => params.skillId,
});

This is how we determine whether the skill is created or not.