chore: wip refactor

The idea here was to reuse the experimental router within the actual
router. This turns out to be a lot of work without any security of
having something working and without breaking changes in the end. So I
think it's better to keep two versions of the createRouter function with
prefix `EXPERIMENTAL_`. In the end, one code base only uses one of the
function so it's fine to keep the code duplicated until v5. This branch
is here as a reminder of the failure.

Author: posva

packages/router/src/experimental/router.ts

@@ -410,6 +410,7 @@ export interface EXPERIMENTAL_RouteRecordNormalized extends NEW_MatcherRecord {
    * Arbitrary data attached to the record.
    */
   meta: RouteMeta
+  parent?: EXPERIMENTAL_RouteRecordNormalized
 }
 
 function normalizeRouteRecord(

packages/router/src/matcher/pathMatcher.ts

@@ -16,6 +16,32 @@ export interface RouteRecordMatcher extends PathParser {
   alias: RouteRecordMatcher[]
 }
 
+export function NEW_createRouteRecordMatcher(
+  record: Readonly<RouteRecord>,
+  parent: RouteRecordMatcher | undefined,
+  options?: PathParserOptions
+): RouteRecordMatcher {
+  const parser = tokensToParser(tokenizePath(record.path), options)
+
+  const matcher: RouteRecordMatcher = assign(parser, {
+    record,
+    parent,
+    // these needs to be populated by the parent
+    children: [],
+    alias: [],
+  })
+
+  if (parent) {
+    // both are aliases or both are not aliases
+    // we don't want to mix them because the order is used when
+    // passing originalRecord in Matcher.addRoute
+    if (!matcher.record.aliasOf === !parent.record.aliasOf)
+      parent.children.push(matcher)
+  }
+
+  return matcher
+}
+
 export function createRouteRecordMatcher(
   record: Readonly<RouteRecord>,
   parent: RouteRecordMatcher | undefined,