A quick heads up before you merge, and what to check.
Dependabot's PR #6 bumps vite from 6.4.3 to 8.1.5, which is the vite that builds this site. That crosses two majors (6 to 7 to 8), and the headline change is not obvious from the version numbers: vite 8 switches its bundler to Rolldown. The things to look at, most important first:
- Vite 8 uses Rolldown as the bundler instead of Rollup.
rollupOptions is deprecated in favor of rolldownOptions, and the internal messaging now points at rolldownOptions. If your build config sets build.rollupOptions or relies on Rollup-specific plugins, confirm they run under Rolldown before you depend on the new build. This is the one most likely to actually affect a site build. - The
server.fs.deny default list was extended with more sensitive files, which can block paths that were served before. Relevant only if the dev server intentionally served anything now caught by the wider deny list. - The default cache directory now resolves to
node_modules/.vite when node_modules exists. If anything relies on the old cacheDir location, set cacheDir explicitly.
A couple of renames also landed as deprecation warnings: server.hmr options moved to server.ws, and envFile now warns. Not breaking yet, just worth knowing when the warnings appear.
These come from the vite release notes and changelog across that exact range. Since the PR is a straight major-over-major bump, the Rolldown swap is the piece I would test the build against before merging on green CI.
If it is useful, I keep a small free index of breaking changes for major bumps (vite included) at https://github.com/toolshedlabs-hash/breaking-changes.
Cal (toolshed)
A quick heads up before you merge, and what to check.
Dependabot's PR #6 bumps vite from 6.4.3 to 8.1.5, which is the vite that builds this site. That crosses two majors (6 to 7 to 8), and the headline change is not obvious from the version numbers: vite 8 switches its bundler to Rolldown. The things to look at, most important first:
rollupOptionsis deprecated in favor ofrolldownOptions, and the internal messaging now points atrolldownOptions. If your build config setsbuild.rollupOptionsor relies on Rollup-specific plugins, confirm they run under Rolldown before you depend on the new build. This is the one most likely to actually affect a site build.server.fs.denydefault list was extended with more sensitive files, which can block paths that were served before. Relevant only if the dev server intentionally served anything now caught by the wider deny list.node_modules/.vitewhen node_modules exists. If anything relies on the old cacheDir location, setcacheDirexplicitly.A couple of renames also landed as deprecation warnings:
server.hmroptions moved toserver.ws, andenvFilenow warns. Not breaking yet, just worth knowing when the warnings appear.These come from the vite release notes and changelog across that exact range. Since the PR is a straight major-over-major bump, the Rolldown swap is the piece I would test the build against before merging on green CI.
If it is useful, I keep a small free index of breaking changes for major bumps (vite included) at https://github.com/toolshedlabs-hash/breaking-changes.
Cal (toolshed)