Wouter van Vliet

@abjugard Interesting, ... I'm not using Azure Functions so there might be some differences in setup; but the tiny test project I used to test Magick on alpine images runs...

I'm also looking for a package that supports parsing of client hints; but haven't been able to find anything yet. I won't expect this will be added to express-useragent though,...

Yes it can, quite easily. Use `swagger-typescript-api generate-templates` to get all the templates, and then use `http-client.ejs` to customize `http-client.ts`

@gustaveWPM Hot take... makes me curious. Would you care to elaborate on why?

> Furthermore, is always pushed onto the [top layer](https://developer.mozilla.org/en-US/docs/Glossary/Top_layer), which is an enough undesirable side effect imo to never want to hear about it. But that's exactly what a dialog...

Looks like #595 bumps to 5.2.2; any reason not to broaden the horizon and allow newer versions as well?

Hi, We're running into the same problem and managed to narrow it down to tsx files that contain a `-` character in the filename.

More specifically; the issue happens when using `export default` syntax in files with kebab-case filenames. The generated code will look like: `hyphen-in-filename.displayName = "hyphen-in-filename";`

Done a bit more digging, and the cause seems to be that react-docgen-typescript sets docComment.displayName to it's best guess, which sometimes is just the filename, and react-docgen-typescript-loader uses this displayName...

I've got the same problem, but was able to work around by using a .cjs config file with an async function as default export. for example: ``` module.exports = async...