Fix: Convert the RegExp to a string

[andyeskridge]

By converting the RegExp to a string webpack stops complaining. I've done some quick testing and it seem that everything is still working, but I would love some other eyes on this.

Because webpack converts globs to RegExp it seems that it executes this RegExp that is just a sting. (https://webpack.js.org/configuration/watch/#watchoptionsignored)

This closes #31

[jaredpalmer]

This worked for me

[deadcoder0904]

@williamluke4 wanna merge & release this one?

Edit

Till then I used commit hash in my package.json:

"next-prisma-plugin": "prisma-labs/next-prisma-plugin#a3c6e044a9b44bfbe6a799e2e2377a15280b1569"

I also tried installing the package like:

$ npm i andyeskridge/next-prisma-plugin#patch-1

However, it didn't help. It gives me:

Error: Cannot find module '\node_modules\next-prisma-plugin\dist\index.js'. Please verify that the package.json has a valid "main" entry

[andyeskridge]

@williamluke4 wanna merge & release this one?

Edit

Till then I used commit hash in my package.json:

"next-prisma-plugin": "prisma-labs/next-prisma-plugin#a3c6e044a9b44bfbe6a799e2e2377a15280b1569"

I also tried installing the package like:

$ npm i andyeskridge/next-prisma-plugin#patch-1

However, it didn't help. It gives me:

Error: Cannot find module '\node_modules\next-prisma-plugin\dist\index.js'. Please verify that the package.json has a valid "main" entry

Yeah the plugin requires a build, while I was waiting for this to be unblocked I published a npm package to use in the meantime. https://www.npmjs.com/package/next-prisma-plugin-webpack5

[deadcoder0904]

Thanks, Andy, was just gonna ask about it now 😂

[DaniGuardiola]

Hi there :) any plans to merge this and create a release? Thank you for fixing this!