Drizzle studio non-functional, but present in package.json

Open
#632 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
Under an hour
Newbie friendliness
55/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
json, typescript
Domain
database, tooling

Research direction

The failing script is the db:studio entry in apps/cms/package.json, which runs drizzle-kit studio. The error says drizzle.config.json does not exist in apps/cms, so check whether a drizzle.config.ts exists there and whether the CLI can take it through --config. Reproduce with pnpm run db:studio. Done means the script starts Studio or the entry is removed from package.json, and the change is explained in the PR since the issue leaves the choice open.

Written by the indexing model from the issue text.

Description

area: developer-experience bug maintenance priority: P2

package.json has and entry for:
"db:studio": "drizzle-kit studio",

If you attempt to use it, you get:
$ pnpm run db:studio

[email protected] db:studio /repos/website/apps/cms
drizzle-kit studio

No config path provided, using default 'drizzle.config.json'
/repos/website/apps/cms/drizzle.config.json file does not exist
 ELIFECYCLE  Command failed with exit code 1.

Either remove it, or make functional.

Dominant language
TypeScript
Stars
1.8k
Forks
219
Avg merge
2d 21h
Merged PRs (30d)
67

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from SonicJs-Org/sonicjs

All issues in SonicJs-Org/sonicjs

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.