-
-
Notifications
You must be signed in to change notification settings - Fork 208
Update to Babel 6? #199
Comments
Yeah been working on it but it will take a while since there's a lot of changes. |
@hzoo Great to hear. 👍 |
@hzoo Are you working on a branch? I would like to help :) |
Yeah was doing it locally. #202 - Also have to make changes in acorn-to-esprima though (which should probably be renamed or maybe removed now) |
waiting for release, babel 6 change too much. my eslint check give me this:
|
@geminiyellow same, disabled linting for now |
All the current tests pass but I'm sure there are a bunch of issues - I can do a prerelease or something if people want to report bugs (or just checkout the pr and test it locally) |
@hzoo ok, please make a prerelease. i will try it locally. |
Thank's @hzoo, sorry was a lot busy though I could help 🙏 Going to test your branch with my projects ;) |
disabled eslint-loader til babel/babel-eslint#199 (sublime linter still working)
- updated to babel 6 - temp disable babel-eslint due to compatible issue babel/babel-eslint#199
@hzoo If there is a lot that needs to be done, it might be worth creating a todo list that people could contribute to. |
Good idea - although the todo list is mostly fixing up the ast in the acorn-to-esprima repo |
I need this fixed as well, really weird |
made a prerelease https://github.com/babel/babel-eslint/releases/tag/v5.0.0-beta1 |
Thanks @hzoo, really appreciated! |
I just tried v5.0.0-beta4 and am still getting the following:
|
Still getting - was it working before? Maybe something in your setup isn't working |
I'm setting this up for the first time as a Browserify user trying to move to Webpack. You may be completely right that something in my setup may be wrong but I was never able to get this working with Babel 6 from when I ported everything over two weeks ago until now in trying the latest release. I've got everything working otherwise except the babel-eslint setup. This is my usage portions that pertain to it:
|
Yeah if you haven't used it before that is a different issue from this - you need to specify the parser. |
I have the parser specified in my .eslintrc:
I meant to say I haven't used Webpack before but I have used Browserify successfully (albeit I'm porting to Babel 6/Webpack together, didn't test Babel 6+ with my Browserify setup). |
As noted in #218 there is an issue with getters/setters |
Published [email protected] which hopefully fixes getters/setters. Going to close this issue for now so if there are other issues open a new issue with the relevant info |
Given Babel 6 was just released, it might be nice to get
babel-eslint
on the board as well.The text was updated successfully, but these errors were encountered: