Tommy

@oleksandr-dziuban I've never used this plugin with React Native so I unfortunately cannot help. So hopefully some other users and RN devs can help with this issue, and if there's...

@axelnormand - Maybe I'm missing something, but what's the benefit from using both the plugin and the config in typescript? I feel like you can do pretty much the same...

Yup, forgot about a webpack compilation. I'm away for the next couple days, but I'll come back to this thread shortly after. Thanks for sharing your config.

With typescript becoming more and more popular every day. I'd love seeing something like this by default in the plugin. If anyone is interested in making a PR.

Did you also add the function to `transformFunctions`? Shouldn't your code be like this? ``` const resolvePath = c => c const ProxyInboxModel = proxyquire('../model.js', { [ resolvePath('../model.js')]: { ......

I believe we do remove `index`? Because it's the default behavior. What situation makes you willing to have an option to decide this?

Interesting, so it's a bit specific to esm I believe. Wonder if we could revert our decision to strip the extension and index name. @fatfisz what do you think?

@fatfisz What do you think? I feel like it could slow down projects compilation if we start checking all paths? At the same time, in big projects, my guess is...

I finally got a use case where I wanted to resolve a relative path as well, but with a specific alias config though. The usecase was to map all `*.css`...

Nvm, it's not safe to run on all paths as is. It can create a breaking changes. Let's say I have an alias `"App": './app`. But then I have a...