Skip to content

v2.5.1

Choose a tag to compare

@michelecanini michelecanini released this 28 Oct 16:39
· 4 commits to main since this release

🌱 npm run db:seed and npm run db:seed:demo work again. Since 2.3.3 both stopped with a usage message instead of seeding: two packages each installed a command called dotenv, and the one that answered did not know the option the scripts used. A PATCH: git pull, npm install. Nothing to migrate and nothing to configure. npx prisma db seed, the command of the first steps, was never affected.

Fixed

  • The two seed scripts load .env and .env.local through Node, as npm run check:deploy already does, instead of a dotenv command. A variable already set in the shell still wins over the files, so DATABASE_URL=... npm run db:seed:demo seeds the database you name
  • dotenv-cli is gone from the dependencies: nothing uses it any more, and it is what made the dotenv command ambiguous