-
Notifications
You must be signed in to change notification settings - Fork 55
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Need a new version pushed to npm #354
Comments
I don't have all the context here. The commit you linked to seems to update the eslint-plugin-react package, not eslint. Is import-js broken for a particular project? We're in the middle of a transition off of eslint. I hope to release something soon (ongoing here: https://github.com/Galooshi/import-js/tree/better-parsing), but right now the current If you want to make a quick-fix, there's the |
Apologies, wrong commit link. 80c378b. Some more context: I was testing the changes to the emacs plugin, and was having issues getting the 'fix' command to work (even in the CLI). I had created a new project using create-react-app followed by an
which stems from use of the local eslint at 2.x. The current master branch already fixes this with the commit above to bump eslint to 3.x (and I worked around it by using a local version with |
Cool, thanks. The problem with the version bump is that it breaks projects using an earlier eslint (I believe). Plus master is full of other changes as well. Expect this to be fixed in 2.0, coming sooooooooon. |
OK! waits excitedly |
facing that problem. Is there any updates? |
I'm hoping to release 2.0 during the day. I just need to run some local testing before I do that. Thanks for being patient! |
I would appreciate if you could take 2.0 for a spin and see if it works out. |
importjs is currently broken using updated eslint configs (such as eslint-config-airbnb) without the update to eslint^3.0.0 (a6f4c67). We should push a new (patch?) version.
The text was updated successfully, but these errors were encountered: