Vlad Shcherbin
Vlad Shcherbin
Even with this DRY helper functions I will still need to use them in every graphql resolver. 😞 I've tried to follow `graphql-api-koa` design philosophy by using `expose` and `extension`...
This also doesn't handle case like above where I need to set custom default error message instead of `Internal Server Error`. You may even want to customize error produced by...
@jaydenseric any update to this? I kinda need this in my app badly 😢
I disagree with you on internalization. An app can be in language different from English and it's quite common to return errors in language of the app, frontend developers can...
A small update: I've being using `graphql-api-koa` in ~5 production apps during past year as well as a few hobby projects. What I've being doing in all of this apps...
Yep, I'll try to create a sample stack repo during the week
I miss this feature so much, hope it will be merged some day. 😞
@ppot hey, any news on this one? 🗞
Same, I believe it's somehow related to webpack. Using `next dev --turbo` fixes the problem 🤔
@balazsorban44 here's reproduction: https://github.com/vladshcherbin/next-13-esm-error as @kevva mentioned, `package.json` has `"type": "module"`