H
H
I have this issue on macOS 10.14.6 Happens on any browser and once it happens none of the different browsers work. It just happens randomly and the server stops responding;...
This looks relevant: https://github.com/vercel/next.js/issues/10061#issuecomment-632077342
The use case I have for this is modularizing my code. In different modules, I have `extend type Query { ...}` but I have to define `Query { }` somewhere...
I just realized the associated diagram on the web page needs to be updated as well; unfortunately, I don't have access to the tools for creating that.
There is also another vector of attack with even a more significant impact: if the legitimate client never uses the refresh token e.g. user leaves their session before the expiry...
I am following the same approach as @epatters ``` "scripts": { "build": "mkdir ./dist && compose index.js --js > ./dist/bundle.js", }, ``` It just seems when referencing an action inside...
I created a ticket for this about three years ago and I was about to create it again now that I am Angular giving another go until I found my...
I'm having this issue with 'Vue' as well; so I wonder if it is not a next.js issue but a vercel dev issue
@pi0 I have this issue on FF as well. In my case at least, once it happens, it just fails across all of the other browsers that I have i.e....
Hi. I see the the PR for this issue is closed: https://github.com/vuetifyjs/vuetify/pull/9912 Could the PR still use a helping hand or is it on track for V3.0.0? Thanks