Previous loaders are included in the filepath passed to Babel plugins

[dallonf]

This issue is described in more detail over here, where I noticed the symptoms: formatjs/babel-plugin-react-intl#5

Basically, I have ts-loader set to run before babel-loader, and a plugin (babel-plugin-react-intl) that depends on file options being passed to it. When babel-plugin-react-intl receives the file information, the filename value is '<project directory>/node_modules/ts-loader/index.js!<project directory>/src/pages/asset/Page.tsx' - which it can't parse.

[johanneslumpe]

Just came across this issue today too - hope this can be fixed soon :)

[benmosher]

eslint-loader as a pre-loader + React Transform Babel plugin + Redbox error-catching with custom styles is how I stumbled onto this; the custom styles file got some crazy generated path on account of the loaders still being in the file path provided to Babel.

I suspect it's a pretty straightforward way to reproduce. I can try to conjure it back up, if that would be helpful.

[Couto]

This is now on v6.2.0
I'm closing this. Please re-open if something comes up