rollup error #12

1034935767 · 2024-06-22T01:48:15Z

I got this error, I know auto import by .nuxt\types\nitro-imports.d.ts
const prismaD: typeof import('../../node_modules/.pnpm/@prisma+nuxt@0.0.30_nuxt@3.12.1_@opentelemetry+api@1.9.0_@parcel+watcher@2.4.1_@types+node@20_rappjaaf4divnx3cq7ck24zofu/node_modules/@prisma/nuxt/dist/runtime/server/utils/prisma.d')['default'].
Maybe should not do this
addServerScanDir(createResolver(import.meta.url).resolve("./runtime/server")); at module.ts.

=========================================

[09:20:53]  WARN  [plugin inject] node_modules/.pnpm/@prisma+nuxt@0.0.30_nuxt@3.12.1_@opentelemetry+api@1.9.0_@parcel+watcher@2.4.1_@types+node@20_rappjaaf4divnx3cq7ck24zofu/node_modules/@prisma/nuxt/dist/runtime/server/utils/prisma.d.ts: rollup-plugin-inject: failed to parse D:/Users/Z/Documents/Workspace/JavaScript/Nuxt/nuxt-demo1/node_modules/.pnpm/@prisma+nuxt@0.0.30_nuxt@3.12.1_@opentelemetry+api@1.9.0_@parcel+watcher@2.4.1_@types+node@20_rappjaaf4divnx3cq7ck24zofu/node_modules/@prisma/nuxt/dist/runtime/server/utils/prisma.d.ts. Consider restricting the plugin to particular files via options.include

t)


1: import { PrismaClient } from "@prisma/client";
2: declare const prismaClientSingleton: () => PrismaClient<import(".prisma/client").Prisma.PrismaClientOptions, never, i...
           ^
3: declare const prisma: PrismaClient<import(".prisma/client").Prisma.PrismaClientOptions, never, import("@prisma/client...
4: export type CustomPrismaClient = ReturnType<typeof prismaClientSingleton>;

============================================

The text was updated successfully, but these errors were encountered:

bbhxwl · 2024-06-24T02:04:42Z

I can run it, but I cannot build it

bbhxwl · 2024-06-24T15:13:19Z

[error] Cannot find module '/drone/src/node_modules/vite/node_modules/rollup/parseAst' imported from /drone/src/node_modules/vite/dist/node/index.js

mueslirieger · 2024-06-26T13:00:40Z

I'm also getting this error and I found that it's happening only when I also use the @nuxt/image module. Loading order of modules does not seem to make an impact.
Here would be a minimal reproduction on StackBlitz https://stackblitz.com/edit/nuxt-starter-dybn1q?file=nuxt.config.ts.
Getting Prisma working with Stackblitz made it neccessary for me to use this extension in Chromium based Browsers (personally using Arc).

Are you also using this module? @1034935767 @bbhxwl

bbhxwl · 2024-06-27T01:11:30Z

I'm also getting this error and I found that it's happening only when I also use the @nuxt/image module. Loading order of modules does not seem to make an impact. Here would be a minimal reproduction on StackBlitz https://stackblitz.com/edit/nuxt-starter-dybn1q?file=nuxt.config.ts. Getting Prisma working with Stackblitz made it neccessary for me to use this extension in Chromium based Browsers (personally using Arc).

Are you also using this module? @1034935767 @bbhxwl

Indeed, I also have this module because I used @ nuxt/ui pro, which includes these.

bbhxwl · 2024-06-27T01:12:07Z

I'm also getting this error and I found that it's happening only when I also use the @nuxt/image module. Loading order of modules does not seem to make an impact. Here would be a minimal reproduction on StackBlitz https://stackblitz.com/edit/nuxt-starter-dybn1q?file=nuxt.config.ts. Getting Prisma working with Stackblitz made it neccessary for me to use this extension in Chromium based Browsers (personally using Arc).

Are you also using this module? @1034935767 @bbhxwl

But there is no problem with the operation, only a compilation error.

1034935767 · 2024-06-27T07:32:09Z

I think it doesn't matter with other modules. Just should not import prismaD.

pvlastaridis · 2024-06-27T12:18:34Z

I got this error, I know auto import by .nuxt\types\nitro-imports.d.ts const prismaD: typeof import('../../node_modules/.pnpm/@prisma+nuxt@0.0.30_nuxt@3.12.1_@opentelemetry+api@1.9.0_@parcel+watcher@2.4.1_@types+node@20_rappjaaf4divnx3cq7ck24zofu/node_modules/@prisma/nuxt/dist/runtime/server/utils/prisma.d')['default']. Maybe should not do this addServerScanDir(createResolver(import.meta.url).resolve("./runtime/server")); at module.ts.

=========================================
[09:20:53]  WARN  [plugin inject] node_modules/.pnpm/@prisma+nuxt@0.0.30_nuxt@3.12.1_@opentelemetry+api@1.9.0_@parcel+watcher@2.4.1_@types+node@20_rappjaaf4divnx3cq7ck24zofu/node_modules/@prisma/nuxt/dist/runtime/server/utils/prisma.d.ts: rollup-plugin-inject: failed to parse D:/Users/Z/Documents/Workspace/JavaScript/Nuxt/nuxt-demo1/node_modules/.pnpm/@prisma+nuxt@0.0.30_nuxt@3.12.1_@opentelemetry+api@1.9.0_@parcel+watcher@2.4.1_@types+node@20_rappjaaf4divnx3cq7ck24zofu/node_modules/@prisma/nuxt/dist/runtime/server/utils/prisma.d.ts. Consider restricting the plugin to particular files via options.include

t)


1: import { PrismaClient } from "@prisma/client";
2: declare const prismaClientSingleton: () => PrismaClient<import(".prisma/client").Prisma.PrismaClientOptions, never, i...
           ^
3: declare const prisma: PrismaClient<import(".prisma/client").Prisma.PrismaClientOptions, never, import("@prisma/client...
4: export type CustomPrismaClient = ReturnType<typeof prismaClientSingleton>;
============================================

Well spotted but how can we force it not to export { default as prismaD } from '../../node_modules/@prisma/nuxt/dist/runtime/server/utils/prisma.d';

bbhxwl · 2024-06-28T05:37:53Z

Do you have a solution?

mueslirieger · 2024-07-01T09:44:46Z

I find it interesting that the application does work for you when running the dev server but compilation fails because in my project neither of those work @bbhxwl

bbhxwl · 2024-07-01T12:42:30Z

I find it interesting that the application does work for you when running the dev server but compilation fails because in my project neither of those work @bbhxwl

Well, yes, it's strange that it can't be officially used, it can only be tested.

david-walter-naptics · 2024-07-01T15:19:01Z

I experience the same error message as OP. In a basically empty new project. In my case there is also this behavior where the build fails but the code runs, meaning for example that it did the migrations into my postgresql db. My package.json is the following:

{
    "name": "nuxt-app",
    "private": true,
    "type": "module",
    "scripts": {
        "build": "nuxt build",
        "dev": "nuxt dev --dotenv .env.local",
        "generate": "nuxt generate",
        "preview": "nuxt preview",
        "postinstall": "nuxt prepare",
        "type-check": "npx nuxi typecheck",
        "lint": "eslint .",
        "start": "node .output/server/index.mjs"
    },
    "dependencies": {
        "@nuxt/eslint": "^0.3.13",
        "@nuxt/ui": "^2.17.0",
        "@nuxtjs/i18n": "^8.3.1",
        "@prisma/nuxt": "^0.0.30",
        "@sidebase/nuxt-auth": "^0.7.2",
        "nuxt": "^3.12.2"
    },
    "devDependencies": {
        "@prisma/client": "^5.16.1",
        "prisma": "^5.16.1",
        "typescript": "^5.5.2",
        "vue-tsc": "^2.0.22"
    }
}

I would love to run nuxt-prisma, it is by far the best solution for nuxt and postgresql.

bbhxwl · 2024-07-01T15:29:25Z

I experience the same error message as OP. In a basically empty new project. In my case there is also this behavior where the build fails but the code runs, meaning for example that it did the migrations into my postgresql db. My package.json is the following:

{
    "name": "nuxt-app",
    "private": true,
    "type": "module",
    "scripts": {
        "build": "nuxt build",
        "dev": "nuxt dev --dotenv .env.local",
        "generate": "nuxt generate",
        "preview": "nuxt preview",
        "postinstall": "nuxt prepare",
        "type-check": "npx nuxi typecheck",
        "lint": "eslint .",
        "start": "node .output/server/index.mjs"
    },
    "dependencies": {
        "@nuxt/eslint": "^0.3.13",
        "@nuxt/ui": "^2.17.0",
        "@nuxtjs/i18n": "^8.3.1",
        "@prisma/nuxt": "^0.0.30",
        "@sidebase/nuxt-auth": "^0.7.2",
        "nuxt": "^3.12.2"
    },
    "devDependencies": {
        "@prisma/client": "^5.16.1",
        "prisma": "^5.16.1",
        "typescript": "^5.5.2",
        "vue-tsc": "^2.0.22"
    }
}

I would love to run nuxt-prisma, it is by far the best solution for nuxt and postgresql.

I also really want to use it, but unfortunately, let's wait for more people to discover this issue.

sahibalejandro · 2024-07-07T05:59:10Z

I'm facing a similar issue, when adding ONLY the @prisma/nuxt module to nuxt.config.ts it works fine, however as soon as I add the @sidebase/nuxt-auth module to nuxt.config.js I get this error when running npm run dev:

RollupError: node_modules/@prisma/nuxt/dist/runtime/server/utils/prisma.d.ts (2:8): Expected ';', '}' or <eof> (Note that you need plugins to import files that are not JavaScript)

1: import { PrismaClient } from "@prisma/client";
2: declare const prismaClientSingleton: () => PrismaClient<import(".prisma/client").Prisma.PrismaClientOptions, never, i...
           ^
3: declare const prisma: PrismaClient<import(".prisma/client").Prisma.PrismaClientOptions, never, import("@prisma/client...
4: export type CustomPrismaClient = ReturnType<typeof prismaClientSingleton>;

Code compilation fails but some how the Nuxt development server runs, I guess it silently fails.

I've tried removing node_modules and package-lock.json and reinstall with npm install but nothing changes. I've also tried to change the order of the modules in nuxt.config.ts but the error persists.

It seems like the @nuxt/image module is not the only one affecting @prisma/nuxt, and could be more.

So far I don't have any other clue on what's causing this.

Here is my package.json

{
  "name": "nuxt-app",
  "private": true,
  "type": "module",
  "scripts": {
    "build": "nuxt build",
    "dev": "nuxt dev",
    "generate": "nuxt generate",
    "preview": "nuxt preview",
    "postinstall": "nuxt prepare"
  },
  "dependencies": {
    "@prisma/nuxt": "^0.0.30",
    "@sidebase/nuxt-auth": "^0.8.0",
    "nuxt": "^3.12.3",
    "vue": "latest"
  },
  "devDependencies": {
    "@prisma/client": "^5.16.1",
    "prisma": "^5.16.1"
  }
}

fix issue prisma#12

ElliottZhao · 2024-07-09T00:39:26Z

I don't understand what's causing this problem, but I noticed in the source code that there's a comment that mentions automatically import the utils directory, but it's implemented as scaning directory. So I made a change here and miraculously it no longer prompts the prisma.d.ts exception on my own computer.
I submitted the RP, can someone please help me see if it didn't introduce additional issues?

sahibalejandro · 2024-07-09T04:20:27Z

I don't understand what's causing this problem, but I noticed in the source code that there's a comment that mentions automatically import the utils directory, but it's implemented as scaning directory. So I made a change here and miraculously it no longer prompts the prisma.d.ts exception on my own computer. I submitted the RP, can someone please help me see if it didn't introduce additional issues?

This is interesting. I'm not very familiar with Nitro config, but it seems like addServerScanDir functions similarly to addServerImportDir. I'm guessing this should be okay since the runtime/server directory contains only the utils directory, and no other directories would be left unscanned. Just trying to understand.

silvesterwali · 2024-07-09T16:24:05Z

i get same error .

sahibalejandro · 2024-07-10T03:03:45Z

For anyone encountering this issue, a temporary workaround is to modify the file node_modules/@prisma/nuxt/dist/runtime/server/utils/prisma.d.ts by commenting out its contents.

We'll need to see if @ElliottZhao pull request gets approved for a more permanent fix.

bbhxwl · 2024-07-10T05:31:09Z

I hope to fix it as soon as possible. I don't know how to use it yet.

NyllRE · 2024-07-18T15:10:44Z

this should be fixed asap the module is unusable

jharrell · 2024-07-18T15:34:14Z

We are definitely looking into this and will review @ElliottZhao 's PR as soon as possible.

Thanks for your patience 🙏

ankur-arch · 2024-07-29T07:13:59Z

@ElliottZhao's PR has been merged and released in version 0.0.34. Let me know if this helps resolve the issue.

ankur-arch · 2024-07-30T07:42:15Z

Closing this, as it should be fixed as of version 0.0.34.

bbhxwl · 2024-07-30T16:58:45Z

Closing this, as it should be fixed as of version 0.0.34.

500
Invalid prisma.rankingLog.count() invocation: Prisma Client could not locate the Query Engine for runtime "rhel-openssl-1.0.x". This happened because Prisma Client was generated for "debian-openssl-3.0.x", but the actual deployment required "rhel-openssl-1.0.x". Add "rhel-openssl-1.0.x" to binaryTargets in the "schema.prisma" file and run prisma generate after saving it: generator client { provider = "prisma-client-js" binaryTargets = ["native", "rhel-openssl-1.0.x"] } The following locations have been searched: /var/www/Nuxt3/.output/server/node_modules/.prisma/client /var/www/Nuxt3/.output/server/node_modules/@prisma/client /drone/src/node_modules/@prisma/client /tmp/prisma-engines

jharrell · 2024-07-30T17:12:21Z

@bbhxwl that sounds unrelated and would need a new issue.

However, it's most likely due to your binaryTargets setting. Have you added the suggested line in your schema.prisma?

binaryTargets = ["native", "rhel-openssl-1.0.x"]

ankur-arch · 2024-07-31T07:33:26Z

@bbhxwl could you verify whether #18 is related to your issue?

fixes #12 and enhancements

github-actions · 2024-11-27T08:31:10Z

🎉 This issue has been resolved in version 0.1.1 🎉

The release is available on:

Your semantic-release bot 📦🚀

quienn · 2024-12-01T05:56:36Z

error is still there in 0.1.2:

  ➜ DevTools: press Shift + Alt + D in the browser (v1.6.1)                                                                                                                    11:54:46 p.m.

✔ Vite client built in 110ms                                                                                                                                                  11:54:49 p.m.
✔ Vite server built in 1281ms                                                                                                                                                 11:54:50 p.m.

[11:54:53 p.m.]  WARN  [plugin inject] node_modules/@prisma/nuxt/dist/runtime/server/utils/prisma.d.ts: rollup-plugin-inject: failed to parse /home/quien/Proyectos/Soluciones/control_valijas/node_modules/@prisma/nuxt/dist/runtime/server/utils/prisma.d.ts. Consider restricting the plugin to particular files via options.include


[nitro 11:54:53 p.m.]  ERROR  RollupError: node_modules/@prisma/nuxt/dist/runtime/server/utils/prisma.d.ts (2:8): Expected ';', '}' or <eof> (Note that you need plugins to import files that are not JavaScript)


1: import { PrismaClient } from "@prisma/client";
2: declare const prismaClientSingleton: () => PrismaClient<import(".prisma/client").Prisma.PrismaClientOptions, never, i...
           ^
3: declare const prisma: PrismaClient<import(".prisma/client").Prisma.PrismaClientOptions, never, import("@prisma/client...
4: export type CustomPrismaClient = ReturnType<typeof prismaClientSingleton>;

$ cat package.json

{
  "name": "nuxt-app",
  "private": true,
  "type": "module",
  "scripts": {
    "build": "nuxt build",
    "dev": "nuxt dev",
    "generate": "nuxt generate",
    "preview": "nuxt preview",
    "postinstall": "nuxt prepare"
  },
  "dependencies": {
    "@prisma/nuxt": "^0.1.2",
    "nuxt": "^3.14.1592",
    "nuxt-auth-utils": "^0.5.5",
    "nuxt-authorization": "^0.3.2",
    "vue": "latest",
    "vue-router": "latest",
    "vuetify-nuxt-module": "^0.18.3"
  },
  "devDependencies": {
    "@prisma/client": "^6.0.0",
    "prisma": "^6.0.0"
  }
}

gsxdsm · 2024-12-01T23:57:07Z

This issue is still here. Delete (or emptying out) prisma.d.ts in nuxt/dist/runtime/server/utils solves it and doesn't seem to have any negative side effects. But it's not a long term solve.

This is HUGELY annoying and making me consider going to Drizzle. Can this be prioritized?

This was referenced Jun 24, 2024

prisma studio start error #13

Closed

Prisma can only run debugging, cannot compile and publish? #14

Closed

mhessdev assigned jharrell Jun 28, 2024

sahibalejandro mentioned this issue Jul 7, 2024

Adding @nuxt/image to my modules causes a RollupError with an unrelated scss file 😶 nuxt/image#1151

Closed

ElliottZhao added a commit to ElliottZhao/nuxt-prisma that referenced this issue Jul 8, 2024

Replace addServerScanDir with addServerImportsDir

1dc68fc

fix issue prisma#12

ElliottZhao mentioned this issue Jul 8, 2024

Fix auto-import for runtime/server/utils #19

Merged

ankur-arch added the bug Something isn't working label Jul 29, 2024

ankur-arch closed this as completed Jul 30, 2024

ankur-arch added a commit that referenced this issue Nov 27, 2024

Merge pull request #62 from prisma/DA-1782

350a324

fixes #12 and enhancements

github-actions bot added the released label Nov 27, 2024

gsxdsm mentioned this issue Dec 1, 2024

Nuxt/Prisma conflict with Nuxt/UI #64

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

rollup error #12

rollup error #12

1034935767 commented Jun 22, 2024

bbhxwl commented Jun 24, 2024

bbhxwl commented Jun 24, 2024

mueslirieger commented Jun 26, 2024 •

edited

Loading

bbhxwl commented Jun 27, 2024

bbhxwl commented Jun 27, 2024

1034935767 commented Jun 27, 2024

pvlastaridis commented Jun 27, 2024 •

edited

Loading

bbhxwl commented Jun 28, 2024

mueslirieger commented Jul 1, 2024

bbhxwl commented Jul 1, 2024

david-walter-naptics commented Jul 1, 2024

bbhxwl commented Jul 1, 2024

sahibalejandro commented Jul 7, 2024 •

edited

Loading

ElliottZhao commented Jul 9, 2024

sahibalejandro commented Jul 9, 2024 •

edited

Loading

silvesterwali commented Jul 9, 2024

sahibalejandro commented Jul 10, 2024

bbhxwl commented Jul 10, 2024

NyllRE commented Jul 18, 2024

jharrell commented Jul 18, 2024 •

edited

Loading

ankur-arch commented Jul 29, 2024

ankur-arch commented Jul 30, 2024

bbhxwl commented Jul 30, 2024

jharrell commented Jul 30, 2024

ankur-arch commented Jul 31, 2024

github-actions bot commented Nov 27, 2024

quienn commented Dec 1, 2024

gsxdsm commented Dec 1, 2024

rollup error #12

rollup error #12

Comments

1034935767 commented Jun 22, 2024

bbhxwl commented Jun 24, 2024

bbhxwl commented Jun 24, 2024

mueslirieger commented Jun 26, 2024 • edited Loading

bbhxwl commented Jun 27, 2024

bbhxwl commented Jun 27, 2024

1034935767 commented Jun 27, 2024

pvlastaridis commented Jun 27, 2024 • edited Loading

bbhxwl commented Jun 28, 2024

mueslirieger commented Jul 1, 2024

bbhxwl commented Jul 1, 2024

david-walter-naptics commented Jul 1, 2024

bbhxwl commented Jul 1, 2024

sahibalejandro commented Jul 7, 2024 • edited Loading

ElliottZhao commented Jul 9, 2024

sahibalejandro commented Jul 9, 2024 • edited Loading

silvesterwali commented Jul 9, 2024

sahibalejandro commented Jul 10, 2024

bbhxwl commented Jul 10, 2024

NyllRE commented Jul 18, 2024

jharrell commented Jul 18, 2024 • edited Loading

ankur-arch commented Jul 29, 2024

ankur-arch commented Jul 30, 2024

bbhxwl commented Jul 30, 2024

jharrell commented Jul 30, 2024

ankur-arch commented Jul 31, 2024

github-actions bot commented Nov 27, 2024

quienn commented Dec 1, 2024

gsxdsm commented Dec 1, 2024

mueslirieger commented Jun 26, 2024 •

edited

Loading

pvlastaridis commented Jun 27, 2024 •

edited

Loading

sahibalejandro commented Jul 7, 2024 •

edited

Loading

sahibalejandro commented Jul 9, 2024 •

edited

Loading

jharrell commented Jul 18, 2024 •

edited

Loading