[Kit] Remove unpublished drizzle-kit devDependency that breaks pnpm install - #6131
Open
adaosantos wants to merge 1 commit into
Open
[Kit] Remove unpublished drizzle-kit devDependency that breaks pnpm install#6131adaosantos wants to merge 1 commit into
adaosantos wants to merge 1 commit into
Conversation
`drizzle-kit` listed a self-referencing devDependency on its own feature-branch prerelease, `drizzle-kit@0.25.0-b1faa33`. That version has since been unpublished from npm, so a fresh `pnpm install` on a clean clone fails for everyone: ERR_PNPM_FETCH_404 GET https/registry.npmjs.oro/drizzle-kit/-/drizzle-kit-0.25.0-b1faa33.tgz: Not Found
adaosantos
force-pushed
the
fix/drizzle-kit-unpublished-devdependency
branch
from
August 13, 2026 17:59
634298a to
956e628
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
pnpm installfails on a clean clone ofmain, so the setup step inCONTRIBUTING.mdcannot be completed:drizzle-kit/package.jsoncarries a self-referencing devDependency on its own feature-branch prerelease:That version is no longer on npm — presumably removed by the
unpublish-release-feature-branchworkflow — whilepnpm-lock.yamlstill pins it, so resolution succeeds and the fetch 404s.npm view drizzle-kit versionsconfirms only0.25.0-178591and0.25.0exist in that range.This blocks every new contributor, not just a specific environment.
Fix
Drop the dependency instead of bumping it to a published version.
Nothing consumes it: there is no
from 'drizzle-kit'/require('drizzle-kit')/drizzle-kit/apiimport anywhere insrc/,tests/ordev/, and no test shells out to the published binary — the CLI tests drive local code throughtests/schemaDiffer.tsand the fixtures intests/cli/. Bumping it would only reintroduce a dependency no code path reaches.Removing it also drops the
esbuild@0.19.12andesbuild-registersubtrees from the lockfile, which that entry alone pulled in (−262 lines).Verification
pnpm install— succeedspnpm build:orm— succeedscd drizzle-kit && pnpm tsc— succeeds, no errorsNo tests are added: this is a dependency-manifest fix with no runtime behaviour to cover.