I upgraded to version 0.27 and after generating a model and running blitz db migrate I get the following error.

Here's the link mentioned in the error: https://www.prisma.io/docs/guides/prisma-guides/prisma-migrate-guides/add-prisma-migrate-to-a-project
blitz db migratemacOS Catalina | darwin-x64 | Node: v14.7.0
blitz: 0.27.0 (global)
blitz: 0.27.0 (local)
Package manager: yarn
System:
OS: macOS 10.15.7
CPU: (12) x64 Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz
Memory: 769.20 MB / 32.00 GB
Shell: 5.7.1 - /bin/zsh
Binaries:
Node: 14.7.0 - ~/.nvm/versions/node/v14.7.0/bin/node
Yarn: 1.22.4 - /usr/local/bin/yarn
npm: 6.14.8 - ~/.nvm/versions/node/v14.7.0/bin/npm
Watchman: Not Found
npmPackages:
@prisma/cli: 2.13.0 => 2.13.0
@prisma/client: 2.13.0 => 2.13.0
blitz: 0.27.0 => 0.27.0
react: 0.0.0-experimental-4ead6b530 => 0.0.0-experimental-4ead6b530
react-dom: 0.0.0-experimental-4ead6b530 => 0.0.0-experimental-4ead6b530
typescript: 4.1.2 => 4.1.2
Please include applicable logs and screenshots that show your problem.
package.json:
{
"name": "mysite",
"version": "1.0.0",
"scripts": {
"start": "blitz start",
"studio": "blitz db studio",
"build": "blitz build",
"lint": "eslint --ignore-path .gitignore --ext .js,.ts,.tsx .",
"test": "jest",
"test:watch": "jest --watch"
},
"browserslist": [
"defaults"
],
"prisma": {
"schema": "db/schema.prisma"
},
"prettier": {
"semi": false,
"printWidth": 100
},
"husky": {
"hooks": {
"pre-commit": "lint-staged && pretty-quick --staged",
"pre-push": "tsc && npm run lint && npm run test"
}
},
"lint-staged": {
"*.{js,ts,tsx}": [
"eslint --fix"
]
},
"dependencies": {
"@prisma/cli": "2.13.0",
"@prisma/client": "2.13.0",
"blitz": "0.27.0",
"react": "0.0.0-experimental-4ead6b530",
"react-dom": "0.0.0-experimental-4ead6b530",
"react-error-boundary": "2.3.2",
"secure-password": "4.0.0",
"typescript": "4.1.2",
"zod": "1.11.11",
"final-form": "4.20.1",
"react-final-form": "6.5.2"
},
"devDependencies": {
"@testing-library/jest-dom": "5.11.6",
"@testing-library/react": "11.2.2",
"@testing-library/react-hooks": "3.7.0",
"@types/jest": "26.0.17",
"@types/react": "16.14.2",
"@types/secure-password": "3.1.0",
"@typescript-eslint/eslint-plugin": "4.9.1",
"@typescript-eslint/parser": "4.9.1",
"babel-eslint": "10.1.0",
"eslint": "7.15.0",
"eslint-config-react-app": "5.2.1",
"eslint-plugin-flowtype": "5.2.0",
"eslint-plugin-import": "2.22.1",
"eslint-plugin-jsx-a11y": "6.4.1",
"eslint-plugin-react": "7.21.5",
"eslint-plugin-react-hooks": "4.2.0",
"husky": "4.3.5",
"jest": "26.6.3",
"jest-environment-jsdom-fourteen": "1.0.1",
"jest-watch-typeahead": "0.6.1",
"react-test-renderer": "16.14.0",
"lint-staged": "10.5.3",
"prettier": "2.2.1",
"pretty-quick": "3.1.0",
"ts-jest": "26.4.4"
},
"private": true
}
Switch back to Prisma 2.12
dependencies": {
"@prisma/cli": "2.12.0",
"@prisma/client": "2.12.0",
Prisma released a new version of their Prisma Migrate tool today which seems to have breaking changes.
switching back to
dependencies": {
"@prisma/cli": "2.12.0",
"@prisma/client": "2.12.0",
has fixed the issue for me
Most helpful comment
switching back to
has fixed the issue for me