Bump vinext from 0.0.50 to 0.2.1 - #32
Conversation
Bumps [vinext](https://github.com/cloudflare/vinext) from 0.0.50 to 0.2.1. - [Release notes](https://github.com/cloudflare/vinext/releases) - [Commits](https://github.com/cloudflare/vinext/compare/v0.0.50...vinext@0.2.1) --- updated-dependencies: - dependency-name: vinext dependency-version: 0.2.1 dependency-type: direct:development update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
dependencies
![devin-ai-integration[bot]](https://avatars.githubusercontent.com/in/811515?s=60&v=4){kind=small}
| "tsx": "^4.23.7", | ||
| "typescript": "5.9.3", | ||
| "vinext": "0.0.50", | ||
| "vinext": "0.2.1", |
There was a problem hiding this comment.
🔍 tsconfig path alias resolution may no longer be provided by vinext 0.2.1
In vinext 0.0.50 the core plugin imported vite-tsconfig-paths directly and, for Vite 8, set resolve.tsconfigPaths: true for the project's environments (see dist/index.js:58,382,409,601 of the 0.0.50 tarball). In vinext 0.2.1 the only remaining tsconfig handling is for loading next.config (dist/config/next-config.js:317-328); the plugin no longer registers vite-tsconfig-paths nor enables resolve.tsconfigPaths for application code, and the dependency moved to an optional peer (which is why this PR's lockfile update deletes vite-tsconfig-paths, tsconfck, and globrex). This repo relies heavily on the @/* alias declared only in tsconfig.json (e.g. app/layout.tsx, app/api/**/route.ts) and vite.config.ts declares no resolve.alias and does not add a tsconfigPaths() plugin. Vite 8 exposes resolve.tsconfigPaths as an opt-in boolean (dist/node/index.d.ts:2016), so unless it defaults to enabled, npm run build/npm run dev could fail to resolve @/... imports after this bump. Worth verifying with an actual install + build before merging (node_modules is not present in the checkout, so this could not be exercised here).
Was this helpful? React with 👍 or 👎 to provide feedback.
| "tsx": "^4.23.7", | ||
| "typescript": "5.9.3", | ||
| "vinext": "0.0.50", | ||
| "vinext": "0.2.1", |
There was a problem hiding this comment.
🔍 Minor-version bump on a pre-1.0 dependency crosses effectively-breaking boundaries
vinext is pre-1.0 (0.0.50 -> 0.2.1), so minor bumps here can contain breaking changes; the release notes include peer-dependency restructuring (vite-tsconfig-paths becoming an optional peer) and Pages/App Router behavior changes such as reactStrictMode now being enforced by wrapping the client root. The repo's Worker entry imports vinext/server/app-router-entry (worker/index.ts:2), so the full local gate described in CONTRIBUTING.md (build, both Worker dry-runs, preflight) should be run against this bump rather than relying on the compatibility score.
Was this helpful? React with 👍 or 👎 to provide feedback.
Bumps vinext from 0.0.50 to 0.2.1.
Release notes
Sourced from vinext's releases.
... (truncated)
Commits
5471b41chore: version packages (#2428)b7455c3fix: fully elide inline type-only import specifiers (#2498)5915c87fix(app-router): limit mounted slot cache variants (#2497)336450afix(config): escape destination query params (#2494)e0db846fix(cloudflare): respect TPR cache opt-outs (#2493)20e1076chore(release): reclassify reactStrictMode entry (#2496)a9a30a5fix(app-router): omit pending RSC cache state for query renders (#2488)6c7b71efix(app-router): isolate global not-found css (#2444)8b12274fix(pages): align middleware data prefetch caching (#2451)6bd1ee0fix(app-router): expose app rewrites to pages data clients (#2468)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)