Closed frankcollins3 closed 1 year ago
bookmarking that I"m surprised squiggle-lines in a package.json isn't a breaking change. it isn't an issue with a dependency ... but still. [10:53pm]
setting prisma here and get an "invalid name" error. the rest of the app runs fine.
this observation didn't age well: bookmarking that I"m surprised squiggle-lines in a package.json isn't a breaking change. [7:39pm]
the proposed approach would be to redo this app by creating a new project and adding the dependencies. set the app up this way, by git cloning an already working nextJS app just because of some versioning issues
ran prisma successfully by changing:
{ "name": "mine-nugget-ts", // change "water app" to "mine-nugget-ts" "version": "0.1.0", "private": true, "type": "module",
✔ Generated Prisma Client (4.6.1 | library) to ./node_modules/@prisma/client in 3.77s You can now start using Prisma Client in your code. Reference: https://pris.ly/d/client
import { PrismaClient } from '@prisma/client'
const prisma = new PrismaClient()
warn Versions of prisma@4.16.2 and @prisma/client@4.6.1 don't match. This might lead to unexpected behavior. Please make sure they have the same version. ➜ next-water-app git:(main) ✗
[7:41pm]
attempting to do: 1: had versioning issues, installed higher macOS, computer couldn't process files.. 2: successfully fixed by downloading an older nextJS repo 'mine-nugget-ts' 3: changed the name to reflect the name app that was being created.
error:
proposed approach: 0: change name back to mine-nugget-ts which was the name this git clone {app} came with (error free)
1: ask chatGPT or stackoverflow. not sure.
2: restart a new project and download these specific versions. git clone old nextJS project to save time at 2am or so last night.