This is a demo post for testing the flow

npx prisma -v Environment variables loaded from .env prisma : 5.7.0 @prisma/client : 5.7.0 Computed binaryTarget : darwin-arm64 Operating System : darwin Architecture : arm64 Node.js : v18.17.0 Query Engine (Node-API) : libquery-engine 79fb5193cf0a8fdbef536e4b4a159cad677ab1b9 (at node_modules/.pnpm/@prisma+engines@5.7.0/node_modules/@prisma/engines/libquery_engine-darwin-arm64.dylib.node) Schema Engine : schema-engine-cli 79fb5193cf0a8fdbef536e4b4a159cad677ab1b9 (at node_modules/.pnpm/@prisma+engines@5.7.0/node_modules/@prisma/engines/schema-engine-darwin-arm64) Schema Wasm : @prisma/prisma-schema-wasm 5.7.0-41.79fb5193cf0a8fdbef536e4b4a159cad677ab1b9 Default Engines Hash : 79fb5193cf0a8fdbef536e4b4a159cad677ab1b9 Studio : 0.495.0

Read more

They are very similar, but an attribute is a "property" with a pre-defined "key" that you set on a native element, while a "prop" is a "property" that you set on a custom element (react functional or class component). So, for example, if you have <img src='foo. png'/> then src is an attribute of the resulting DOM node.

Read more

nice trying

test : import dynamic from 'next/dynamic' const DynamicHeader = dynamic(() => import('../components/header'), { ssr: false, })

Read more