Jonas Kello

Seems like a resolver plug-in does not get any information about the webpack context or anything else that we could use to make a sane default to use as a...

I think this is related to the change made in #85. @voliva @Rush Do you have an idea why this seems to be happening now after #85 has been merged...

Now that nested mainfields is supported in tsconfig-paths 4.1.0 you could try to upgrade and see if the types match better.

Seems like the consensus is that this is a good feature to add. I'm planning to make a new major release because of #90. @lynch16 Could you add information in...

> Apparently it's not that easy. TsconfigPathsPlugin is a plugin for enhanced-resolver and doesn't get access to webpack config options Yes, that is why it was not done from the...

It could be implemented as a middleware which you could add if you are OK with the memory overhead of buffering the request body. If you add middleware "buffferRequest" then...

Actually the suggestion to have it as a middleware was because I thought that would give the ability to opt-in :-). I was thinking, since middleware can be conditionally applied...

Here's an attempt at a buffering middleware package: https://github.com/jonaskello/shelf_buffer_request It re-implements the Request class which means it will break on any changes to the Request class.

This seems like a really nice extension. Unfortunately it does not work for me either. I use gitlab and have set the same as @Niels-NTG but I get an error...

I also have Windows 10, so I tried the same thing there but same result. Error "Unknown Git provider. Error: unknown Provider".