Description
At the moment it's quite hard to debug HTTP errors because the only information we get is:

HTTP/1.1 400 Bad Request returned for "https://example.com/".

It would be nice to have an opt-in option that would automatically open response payload and headers in order to log them in Sentry for example. It may require to handle a max lenght on the response payload.

We would like to avoid confusion like we have in webpack-contrib/webpack-bundle-analyzer#185

We could document statsFilename and reportFilename options allowing the use of an absolute file path like /path/to/folder so that people would know it's supported.

Let us know in this issue if you would like to contribute to this!

Description of the issue

I'm building in a clean virtualenv with pyinstaller test.py --windowed
I can't launch the .app bundle by double-clicking nor with open ./test.app in Terminal.
It works fine if I run ./test.app/Contents/MacOS/test

Context information (for bug reports)

• Output of pyinstaller --version: 4.0
• Version of Python: 3.7.7
• Platform: macOS 10.14.6

I guess MicroBundle hasn't support TypeScript 4.x, because I got an error:

rpt2: config error TS5023: Unknown compiler option 'jsxFragmentFactory'.

Short description of what this feature will allow to do:
When bundle asked for directory to generate controller, why not to create the sub folders if not exist, instead of threw exception?

Example of how to use this feature
This is just one kind of example of integration:

Which directory do you want to generate "DashboardController" in? [src/Controller/Admin/]:
> 

The "src/C

It could be great to leverage these metadata, notably when using jms virtual properties.