File-based routing does not support prefixed dynamic segments

[tonyfromundefined]

Hi team, thanks for building Waku.

I’m seeing a limitation in file-based routing: dynamic segments appear to work only when the segment is exactly bracketed (e.g. [param]), but not when a static prefix is attached (e.g. prefix[param]).

Expected behavior

File-based routing should allow dynamic segments with static prefixes, so URLs like:

• /@value
• /u-value
• /org-value

can be represented directly in route segment naming.

Actual behavior

Prefixed dynamic segment patterns are not recognized correctly.
Only plain dynamic segments (without prefix) seem to be supported.

Why this matters

Many URL conventions rely on prefixed identifiers (for example handle-like URLs). Without prefix support, developers must change URL structure or add extra routing workarounds.

Request

Could Waku support static-prefix + dynamic-segment patterns in file-based routing, or provide an official recommended pattern for this use case?

[dai-shi]

@tylersayshi What do you think?

[tylersayshi]

To make sure i follow this pattern... You may use this to differentiate: /about from /@[user] on a site, correct?

That way it let's the waku router handle the about page as different from a user details page routed like this?

this is an issue that seems to describe the same thing as i understand the problem: TanStack/router#707

Is this all on the right track for what you're thinking @tonyfromundefined?

[tonyfromundefined]

@tylersayshi The issue you shared is accurate. I hope this feature will be supported.