attempting to do:
fixed issue with routes going bad because of too many prisma instances.
error:
/LogInOutGoogle.tsx is the file from the react-express of this same app (loaded with import errors)
This file has not been causing problems but suddenly started causing an "element string" error
// note this file works in react-express with no problems.
proposed approach
this file is being copied (and refactored) but for nextJS.
can now use the file in vs code editor without it being tied to the rendering of components.
strange that i've been copying this same file in that same file scope for a few days and suddenly have a problem
don't know if it has to do with prisma connections
attempting to do: fixed issue with routes going bad because of too many prisma instances.
error: /LogInOutGoogle.tsx is the file from the react-express of this same app (loaded with import errors) This file has not been causing problems but suddenly started causing an "element string" error // note this file works in react-express with no problems.
proposed approach this file is being copied (and refactored) but for nextJS.
changed path from: 👎 /components/loginoutgoogle/loginoutgoogle.tsx 👍 desktop/loginoutgoogle.tsx
can now use the file in vs code editor without it being tied to the rendering of components. strange that i've been copying this same file in that same file scope for a few days and suddenly have a problem
don't know if it has to do with prisma connections