Adam Mcgrath

Similar issue using `EventEmitter` default export, steps to reproduce: ([email protected] / [email protected]) ```shell $ npx create-next-app@latest turbo-test $ cd turbo-test $ echo "const EventEmitter = require('events');\nexport class Foo extends EventEmitter...

👋 @axhl You don't need to provide a custom `getToken` option to `express-jwt` (your custom implementation is wrong, it needs to split out the `bearer` string from the authorization header)....

Hi @axhl - can't see anything wrong with your code. Happy to debug a sample project if you can share a minimal reproduction of the issue

@axhl - no problem It doesn't sound like you need `express-jwt` for that. > Any thoughts on how to best wrap wrap sockets with jwt-verification? I'm not sure about graph-ql...

Hi @BitPatty - thanks for raising this The session store implementation is pretty lightweight at the moment and has the extensibility points for you to add this yourself should you...

@BitPatty - we're not looking to add this ourselves so closing. In general, we tend to use express-session as a guide for feature parity and since this isn't included in...

Hi @Stavtastic - thanks for raising this > npm ERR! Found: [email protected] > npm ERR! node_modules/express > npm ERR! express@"~4.16.1" from the root project This package requires `express@>= 4.17.0` and...

Hi @Stavtastic Could you run `npm ls express`? The error `express@"~4.16.1" from the root project` is telling me that you have `[email protected]` installed in your root project

Hi @Stavtastic - thanks for sharing that I can't explain why you're getting an error that says `Found: [email protected]` when you only have `4.18.1` installed - perhaps you should delete...

Closing due to innactivity