React Router v7 (and others) not receiving path properties

[pakeerathanchandrabalael]

Bug Report

For more information, see the CONTRIBUTING guide.

Prerequisites

• Can you reproduce the problem in a MWE?
• Are you running the latest version?
• Did you perform a search in the issues?

Environment Details and Version

• Piral.Blazor: latest
• piral: latest
• Blazor: WebAssembly
• OS: Windows/Mac
• Browser: Chrome/Firefox

Description

Upgrading to React Router v7 is currently not possible when using Piral.Blazor because the package depends on piral instead of @piral/core.

The piral package tightly couples routing behavior and internally manages React Router, which prevents consumers from configuring or replacing the router. React Router v7 introduces breaking changes that require explicit router control, which is not achievable with the current Piral.Blazor dependency setup.

As a result, Piral.Blazor consumers are blocked from upgrading React Router and modernizing their React stack.

Steps to Reproduce

1. Create a Piral-based application using Piral.Blazor
2. Attempt to upgrade react-router / react-router-dom to version 7
3. Observe dependency conflicts and/or incompatible routing behavior caused by Piral’s internal router

Expected behavior

Piral.Blazor should allow host applications to control routing so that:

React Router v7 can be used
Routing behavior can be customized or replaced
Consumers are not locked into Piral’s routing implementation

Actual behavior

React Router cannot be upgraded beyond v5
Routing is tightly coupled to Piral internals
Host applications cannot configure or override the router

Possible Origin / Solution

Piral.Blazor could be made routing-agnostic by:
Depending on @piral/core instead of piral, or
Providing a way to inject or configure the router externally, or
Decoupling routing concerns so the host application owns router setup

This would unblock React Router v7 upgrades and improve long-term compatibility.

[FlorianRappl]

How is Piral.Blazor dependent on piral? There is piral-blazor but that is a plugin and can be used with piral-core (it also only has a dev dependency on piral-core.

So nothing prevents you to use piral-core already - no need for full Piral. Hence, it already works fully with React Router v7.

Otherwise, provide a MWE to reproduce what you have in mind.

Please specify what you mean with the Piral.Blazor package. What is this? Piral.Blazor.Core? This is a NuGet package and has no dependency whatsoever on piral or any other npm package.

[pakeerathanchandrabalael]

When using Piral.Blazor with React Router v7, Blazor pages fail to receive route parameters correctly.
This appears to be caused by Piral.Blazor relying on the legacy React Router v5 match object, which no longer exists in React Router v7. While Piral core itself supports newer React Router versions, the Blazor integration still assumes the old routing shape.

Piral.Blazor/src/Piral.Blazor.Utils/PiralRouteParameterAttribute.cs

Line 19 in 4f797a2

: base($"match.params.{propertyName}")

[FlorianRappl]

Fair enough. However, I'm not sure if this can generally be fixed. You can just integrate a similar solution (such as the referenced attribute) in your code.

I'll need to think about alternatives / using the context with the generic navigation API.