Running nuxt build when @prisma/nuxt is listed in the modules in nuxt.config.ts deletes other nuxt modules

[damisparks]

The issue is still happening. It is related to #22.
However, it stated that it was fixed on the PR #62
The update is available in v0.1.1 as stated here #62 (comment)

Recommendation

Use option B as workaround as suggested in the closed issue #22
Option B works for me. Hence, I got rid of the @prisma/nuxt module.

[ankur-arch]

Hey @damisparks 👋,

Thanks for reporting this issue! Could you try out the dev release @prisma/[email protected] and let us know if it resolves the problem for you?

Looking forward to your feedback!

[minhlucvan]

I am facing the same issue, tried @prisma/[email protected] but no luck

[ankur-arch]

Thanks, @minhlucvan! 🙏 Could you let me know which package manager you're using?

Additionally, would it be possible for you to share a reproduction repo or example so I can test for a fix on my end?

[ankur-arch]

Hey folks 👋,

@minhlucvan, are you still encountering this issue with the latest version (v0.2.0)?

[damisparks]

@mhessdev how is this issue labelled as not planned?

[jharrell]

Hi @damisparks

We've marked this as closed because we cannot reproduce the issue. Could you please help us by providing a reproduction so we can dig into this further?

[mhessdev]

Yup, just like @jharrell said—we tried multiple times to follow up and get more information, but we couldn’t reproduce the issue, so we closed it. If we receive more details and a proper reproduction, I’d be more than happy to reopen this. @damisparks

[damisparks]

@mhessdev I was out on vacation. I will send a reproduction as soon as possible.
However, it does not mean an issue should be closed as planned with a single comment.
I would suggest "Closing issue due to lack of activity." as a closing comment.