V3: regexparam-based route patterns

[molefrog]

Removes default matcher and replaces it with regexparam

Breaking changes

Matching

• no plus sign modifiers "/:user+"
• no named wildcards "/:user*"
• no optional wildcards "/*?" (yet! see Optional wildcards lukeed/regexparam#25)
• "/users/:id-:name" doesn't work. But, this is supported by path-to-regexp
• when pattern ends with a trailing slash, it matches both "/home/" and "/home", but I suppose it is a better DX
• router no longer accepts matcher prop. Instead, there is a parser prop that allows to customize pattern parsing. Now it is easier to integrate with path-to-regexp

Base paths

• Routes can no longer refer to absolute paths (e.g. ~/home). Why? Because when you are inside a nested context, the content won't be rendered anyway and it requires additional work to support it in regexparam

Modules

• wouter/matcher has been removed

TODO

• TypeScript types
• Type specs for useRoute

Further improvements

1. Memoize constructed patterns: don't parse the string when pattern doesn't change
2. useRoute should not work with falsey patterns, while Route should always render when pattern isn't provided

[github-actions]

size-limit report 📦

Path	Size
packages/wouter/esm/index.js	1.39 KB (-9.69% 🔽)
packages/wouter/esm/use-location.js	664 B (0%)
packages/wouter-preact/esm/index.js	915 B (-14.25% 🔽)
packages/wouter-preact/esm/use-location.js	200 B (0%)

[molefrog]

@jeetiss Hi, here are the things I need your help with:

• Review the PR. Did I miss anything?
• Make vitest ignore old type tests and drop lint-types command in favour of test-types

[jeetiss]

I dropped the cache and almost all tests work now, could you fix last one in wouter-preact package

wouter/packages/wouter-preact/test/preact.test.tsx

Line 41 in 3dd87a7

<Route path="/:anything*">Nothing was found!</Route>

(as I understand named wildcard params doesn't supported by parser)

i think it is better to disable tests for types now (or merge with red ci) and i going to try to fix them in separate PR

[molefrog]

i think it is better to disable tests for types now (or merge with red ci) and i going to try to fix them in separate PR

This test does work for me, how do I clean the cache?

[molefrog]

I figured it out! The test has been fixed.

[molefrog]

Apparently, there was no actual task for linting types on CI 😄