-
-
Notifications
You must be signed in to change notification settings - Fork 121
"Module parse failed" #66
Comments
This is strange, I've got exactly same setup and don't have any issues. Maybe you need |
@nkbt I will try to create a repo with example witch causes this error. Let me some time to do it. |
It seems you just need babel-eslint as a parser for eslint ;) |
I have the same issue even if I add
|
What is your input file that trigger an "Unexpected token" issue? |
It fails on this line and it works fine if I remove the preloader:
And it says:
|
You don't have this issue if used as a loader before (=> after in the array definition) of babel-loader? |
I do have it in this case as well. |
The issue seems related to eslint. Not this loader. |
@MoOx I don't get this issue using |
@MoOx I seems that I also don't have it using |
I have the exact same issue with all the latest packages installed. Using eslint-loader as a preloader fails! |
@MoOx please reopen it until it will be fixed. |
Would love to re-open, but I don't have sufficient rights to do so! Let me know. Thx. |
Can someone open a PR with a failing test? |
Having the same problem |
This module is open source and covered by tests. It is very easy to start working on it: clone the project, the So if you encounter a bug, please take the time to fix it (reminder: Open Source projects work even better with multiples contributors). If don't want to take the time to fix it because you have others priorities, at least make a pull request with a failing test to expose the bug to the world in order to facilitate things for people that will fix it. Thanks ! |
Hi I have the same issue. I wasn't able to run the tests without errors yet. So I've create the repository which demonstrates the bug https://github.com/Halama/eslint-loader-debug |
Thanks a lot, that will helps. It's look like it's related to your version of babel. Can everyone involved here tell which version of babel you are using? babel@6? (I still use babel@5, that probably why I don't have the issue yet) |
This might be related babel/babel-eslint#199 / babel/babel-eslint#202 but I am not sure |
@MoOx I'm using |
|
So like I said, it looks like it is related to the babel-eslint issue mentioned above (not upgraded to babel 6 yet). |
I don't use {
"babel": "^5.8.29",
"babel-core": "^5.8.30",
"babel-loader": "^5.3.2",
"eslint": "^1.7.3",
"eslint-loader": "^1.1.0",
"webpack": "^1.12.1"
} I have the same issue using |
@MoOx Could you please tell us about the progress? |
I didn't do anything yet because I don't have the issue with all my current project atm. Also see #66 (comment) if you want to help. |
Everything is now working great for me after upgrading to the latest babel, etc.. Thanks. G. |
Problem was in babel-loader, for babel@5 you may use [email protected] it works fine with preLoaders |
Thanks for reporting this babel issue. |
same problem here after migrating to Webpack 2.0 even with babel-loader 6 and 7
"babel-cli": "^6.18.0", "eslint": "^3.12.2",
|
@stilllife00 did you find out how to fix it? |
OK my issue was that I was using rules + loaders at the same time. Only using rules fixes it! |
Using of "preLoaders+loaders" causes "Module parse failed":
The text was updated successfully, but these errors were encountered: