v5.1.3
v5.1.3
Released: 2026-10-26
Bug Fixes
Windows:
zfb buildandzfb devnow resolve packages installed as pnpmlink:dependencies that point outside the project, such as a locally linked@takazudo/zfb. pnpm creates these as relative symbolic links. Windows resolves such a link against the path as traversed, so reached through the bundler shadow'snode_modulesjunction it pointed at a directory that does not exist, and esbuild reportedCould not resolve. When a top-level or scopednode_modulesentry is a relative link that leavesnode_modules, the shadow'snode_modulesis now a real directory, and each entry in it is a junction to that entry's real target. Linux and macOS are unchanged (33ff33d7c, 58bfcdf01, #4537).Rolldown: unresolved-import diagnostics now print locations relative to the project with
/separators on Windows (for examplecomponents/), as esbuild does. An absolute fallback location keeps its native spelling (4398090a5, 1b7efe049, #4538).box. tsx: 3: 6: Rolldown: the build metafile's
outputskeys and the paths of internal output imports (emitted chunks and copied files) now come from one helper. They match byte for byte on every platform, keeping native separators like esbuild v0.25.12's absolute metafile paths, including for chunk names that contain a directory (b52f4de81, 1b7efe049, #4538).