chore(deps-dev): bump @point0/core from 0.1.12 to 0.2.8 in the npm group across 1 directory

[dependabot]

Bumps the npm group with 1 update in the / directory: @point0/core.

Updates @point0/core from 0.1.12 to 0.2.8

Changelog

Sourced from @​point0/core's changelog.

0.2.8 — 2026-07-20

• route0 bumped to ^0.3.0, where a path param carries one descriptor — { required, type }, plus values when it is restricted to a set.
• Fix: the OpenAPI path template is built from the route's tokens instead of a regex over the definition string, so a value constraint or a trailing ? no longer leaks into it. /api/posts/:kind(new|top)/:id documented itself as /api/posts/{kind}(new|top)/{id}, and /api/x/:id? as /api/x/{id}?.
• A param restricted to a set now reaches the OpenAPI spec as a real JSON Schema enum, without declaring .params(...) by hand.

0.2.7 — 2026-07-20

• Page routes are matched by route0 instead of by the router's own path parser. A page's <Route> was handed the raw definition string, which wouter re-parses with regexparam — a second, approximate matcher running beside the one point0 already trusts everywhere else. Layouts had always used route0's real RegExp; pages now do too. The two only agreed for plain routes: given /:locale(ru|en)?/author, regexparam minted a param key literally called locale(ru|en) and matched /fr/author, while route0 correctly rejected it — so the page rendered for a URL the framework considered a 404, with params it could not supply.
• Upgraded to @1gr14/route0 0.2, which brings params constrained to a value set — :locale(ru|en) and :locale(ru|en)? — enforced in matching, building, schema validation, the emitted JSON Schema and route ordering, and narrowed to the literal union at the type level. Constrained params flow through the compiler untouched, so a basePath, a nested layout and a synthesized endpoint route all carry them. route0 0.2 also fixes the route ordering that let an optional leading param swallow every single-segment top-level route, and now rejects a route definition that names the same param twice — previously the second occurrence silently overwrote the first, so one of the two segments could never be filled independently.
• The dev proxy no longer cuts long-polls at Bun's idle timeout.
• bunServeConfig is typed as a partial override.
• The compiler resolves imports without the TypeScript compiler API.
• The toolchain guard only guards the tsc of packages that actually run it.

0.2.6 — 2026-07-14

• .scrollPosition() now actually restores a custom scroll container — it never did. A page is code-split, so its collection record holds nothing but the chunk's loader until something loads it, and on the client that only ever happened on a navigation's prefetch — never for the page the server rendered. So the lookup found no point, and silently fell back to the window: the capture stored the window's offset instead of the container's, and the restore moved the window instead of the container. Scroll restoration now loads the page's chunk before it decides anything, and while that is in flight the lookup answers "not yet" rather than "the window" — "we don't know yet how this page scrolls" and "this page scrolls the window" are different answers, and collapsing them is what scrolled the wrong thing and stored the wrong offset. A code-split page's .scrollRestore() policy is honoured for the same reason: it lives in the chunk, the decision is taken once, and it used to be taken from the default policy. And a

... (truncated)

Commits

• acd5448 chore(release): v0.2.8
• fe2aaea fix(openapi): build the path template from the route grammar
• 5986912 chore(release): v0.2.7
• d6cb654 fix(react-dom): match page routes through route0 instead of regexparam
• 6b2680d fix(compiler): resolve imports without the TypeScript compiler API
• c5f6f7c chore(release): v0.2.6
• 90d9e5c fix(core): let the browser restore a document load, and make .scrollPosition(...
• 9c92864 chore(release): v0.2.5
• 5f94c73 chore(release): v0.2.4
• 09361ba chore(deps): bump @​1gr14/route0 to ^0.1.3 in the catalog
• Additional commits viewable in compare view

[dependabot]

Looks like @point0/core is no longer updatable, so this is no longer needed.