Repository navigation
v2.5.1
🌱 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
.envand.env.localthrough Node, asnpm run check:deployalready does, instead of adotenvcommand. A variable already set in the shell still wins over the files, soDATABASE_URL=... npm run db:seed:demoseeds the database you name dotenv-cliis gone from the dependencies: nothing uses it any more, and it is what made thedotenvcommand ambiguous