Changelog
vureact adheres to the Semantic Versioning 2.0.0 specification.
- The latest version is at the top
- Historical versions are listed in reverse chronological order
- For more complete release details, please refer to
packages/router/CHANGELOG.mdin the repository
v2.0.0 - 2026-03-29
✨ New Features
- Removed the
@vureact/router/type-compatsubpath export. All Vue Router-style types are now exported from@vureact/router. - Renamed types:
CreateRouterOptions->RouterOptions,RouterInstance->Router,RouteConfig->RouteRecordRaw. useRouter()now returns the mainRoutertype, aligning semantically with the return value ofcreateRouter().- Added
RouteLocationOptionsand standardizedRouteLocationRaw = string | RouteLocationOptions.
Migration Guide
Upgrading from v1.x to v2.0.0:
- Change all
import type { ... } from '@vureact/router/type-compat'to import from@vureact/router. - Update type names:
RouterInstance->Router,CreateRouterOptions->RouterOptions,RouteConfig->RouteRecordRaw. - Check usage of
useRouter()to ensure no dependency on the old return type name.
v1.1.1 - 2026-03-20
🐞 Bug Fixes
- Fixed the issue where the
componentoption in route configuration could not correctly recognize React higher-order components such asmemo,forwardRef,lazy
v1.1.0 - 2026-03-20
✨ New Features
- The
componentoption in route configuration now supports direct use of React component functions (e.g.,component: App)
🚀 Improvements
- Refactored the
convertRoutefunction to improve the processing logic for component types - Updated the
RouteRecordRawtype definition;ComponentTypenow supports theFunctionComponenttype - Improved the
buildResolvedTofunction to enhance the robustness and null value handling of path resolution - Improved the code organization structure to enhance maintainability and readability
🐞 Bug Fixes
- Fixed type import paths to ensure correct module dependencies
- Improved route matching logic to ensure more accurate route resolution
- Fixed component rendering logic to correctly handle various component types
