Jocelyn Badgley

Sorry, I just realized this was the generator repo, not the express repo. That changes things a little... The generator should prompt from a list of popular choices.

I think I'm leaning towards number 3. It's the most consistent with the way handlers are currently bound to routes. Is there a reason `methods()` wouldn't just take the function...

We have also have been hitting this bug for a while now. Thankfully JSS traps it and just spits out a warning, but it'd be nice to see those warnings...

I also got bit by this bug after upgrading my project from 3.1.1 to 3.1.8. I downgraded back to 311 and it started working again. I can also confirm that...

I just ran afoul of this, as well. @otakustay did you ever find a solution?

I've managed to figure out that this is specifically an issue with the resolver not following symlinks when ReactRefreshWebpackPlugin is in use.

@tibotiber I haven't run this code, but this _should_ do what you need. ```jsx import { forwardRef } from 'react'; import hoistNonReactStatics from 'hoist-non-react-statics'; import * as Sentry from '@sentry/react';...

Just gonna add a few keywords here for google, because it took me WEEKS to find this issue: `graphql-tag` default export import `TypeError: graphql_tag__WEBPACK_IMPORTED_MODULE_0__ is not a function`

I've created a really small reproduction case of this. I was able to make it happen even with local dependencies. https://github.com/ZenTwipped/webpack-default-repro Just `npm install` and `npm start`. The page that...

I've been able to figure out that the issue is in the detection of exportsType of a shared module when passing through from another shared module, it comes back as...