Skip to content
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

Crash when trying to select which option to import from #22

Open
hexsprite opened this issue Aug 27, 2017 · 6 comments
Open

Crash when trying to select which option to import from #22

hexsprite opened this issue Aug 27, 2017 · 6 comments

Comments

@hexsprite
Copy link

hexsprite commented Aug 27, 2017

image

After I get this window when selecting either Fix All Imports or Import Word, the cursor will flash a single time and then the editor window will lock up and then Atom will say it crashed.

@trotzig
Copy link
Contributor

trotzig commented Aug 28, 2017

Ouch.

Can you check what version you are on? We made some changes to the underlying import-js lib around how ambiguous imports are handled in 2.7.0, it was released in v0.11.0 of the atom plugin.

@hexsprite
Copy link
Author

Atom 1.19.3 with atom-import-js 0.11.0

@trotzig
Copy link
Contributor

trotzig commented Aug 28, 2017

Thanks. I'll give that combo a try.

@trotzig
Copy link
Contributor

trotzig commented Aug 28, 2017

The same setup doesn't lead to any issues for me (I did however run into issues installing the atom-import-js plugin though, had to rebuild the package to make it work).

I wonder if there's something corrupt in your cache... Import-js will start a background process indexing all your modules and their exports. There is a way to clean this cache, I think it might be worth doing that. Either run npm install -g import-js && rm $(importjs cachepath) from the root of your project (same folder as where the package.json file is in). Or go to the tmp folder of your os and look for an importjs*.db file and just remove it. You'll have to restart atom after doing that.

I'm mainly using the vim plugin for import-js, apologies for not being completely up-to-date.

@hexsprite
Copy link
Author

I tried clearing the cache. That didn't work. But I did disable some packages and that seemed to make the difference. I wasn't nearly as systematic as I could have been so I'm not sure exactly which one caused the problem but it seems solved for now. If I don't have any more problems I'll close this in a couple days. If I can figure out which are some likely incompatible packages I'll let you know as well.

@trotzig
Copy link
Contributor

trotzig commented Aug 30, 2017

I understand. Often times, these things are hard to isolate. I'm glad you have a working setup though. And let us know if it starts happening again!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants