Tommy
Tommy
Isn't this a webpack issue? Do you see it reloading, or is the plugin compiling the path incorrectly? I don't have any quick project with webpack dev server to test...
Not that I'm aware of. I'm sorry. I remember of some discussions about displaying a warning when a collision like that happen. But in general, it's better to prevent those...
If the module lives in another project, shouldn't the external project provide you compiled source? If it provides you the source, which also use module-resolver, you can use their own...
@SandHilt Are you saying that the extension is required for the browser to work properly? Because in node, the `.js` and `.json` extention are the defaults and not needed at...
We talked a bit about that plugin here #180... A globing system is interesting. I'd definitely accept a PR to add the feature. It shouldn't be that much complicated... right...
Oh yeah I took a deeper look at the glob plugin. It does more than I thought since it gives you all matches. I feel like it's outside of the...
Hmm.. Yeah.. this sucks for windows :/ And it would definitely be great to support Wallaby. Maybe we could use a custom syntax instead of the usual `\\n` to prevent...
@fatfisz Another solution would also be to replace the `\\n` from the regexp into `$n`. That's what jest uses with their `moduleNameMapper` option for example.
Hmm.. Interesting. If you don't destructure it, does it work?
I agree. We should have a debug option in the plugin which output relevant information. To test a single file though, you can already do that using babel-cli.