Lila Rest
Lila Rest
@ljharb Indeed, I tried that already, it silents the error and seems to work at runtime (for now). So this issue is of low severity as we are not blocked...
So I managed to solve the issue with the following Webpack config in my `next.config.mjs` file. ```js // ... webpack: (config) => { // 'traverse' depends on 'is-async-function' and 'is-generator-function,'...
I just found in a random place in the docs that the valid syntax to achieve that is: ```prisma @@allow("read,update,delete", auth() == this) ``` So no issue here, just require...
> ZenStack combines all rules in a model together and injects into a Prisma query (for better performance); so when a violation happens, it doesn't really know which rule caused...
@ymc9 That's super interesting, and makes total sense, thanks for taking time to explain. I don't neither see a simple solution to _precisely_ solve that problem, but an intermediary way...
Update on this, I've been confused because some functions of the Clerk server library were producing the same error, once this solved, the only way I've managed to make the...
Hey @andriytyurnikov and @stormwarning, thanks for your input here! I've identified that the above error was due to the plugin function no longer receiving the `e()` function as a parameter....
I've seen that you pushed some updates yesterday @stormwarning, did this included the patch to this bug? Or should I maintain a version of this plugin in our monorepo as...
@stormwarning A path to a TS config
Same here @ivanfgm! Have you tried once deployed to CF network?