@prisma/config

post-install hook would run prisma generate

prisma migrate would run prisma generate and prisma seed

prisma generate --data-proxy

prisma generate --accelerate

prisma generate --no-engine

prisma generate --allow-no-models

prisma db pull --local-d1 This parameter no longer exists but equivalent functionality can be implemented by defining a config file with a connection string for the local D1 database. We provide a helper function listLocalDatabases in the D1 adapter to simplify the migration:

prisma --[from/to]-schema-datamodel: This is now replaced with just --[from/to]-schema. The usage is otherwise the same.

prisma --[from/to]-url, prisma --[from/to]-schema-datasource: These are now replaced with --[from/to]-config-datasource. The user is expected to populate the datasource in the config file and use the new flag. We no longer support diffing two different URLs/datasources, since only one config can be used at a time.

prisma --[from/to]-local-d1: These are now replaced with --[from/to]-config-datasource. The user is expected to populate the datasource in the config file and use the new flag with a minor complication due to the fact that it needs to reference the local D1 database. Our listLocalDatabases helper function can be used for that, analogously to the db pull --local-d1 example above (where the user sets the datasource URL to file://${listLocalDatabases().pop()})