Open despairblue opened 9 years ago
Have you tried to build Nuclide from source?
Nope, should I uninstall all nuclide packages before attempting this?
Or does it install that packages into some other path and open atom with another "user profile"? Not quite sure what difference building the packages should make.
EDIT: nevermind, I read the README now.
Uninstall everything through the GUI or by rm -r ~/.atom/packages/nuclide-*
, than try installing from source. I am not sure myself about the difference but it worked for me.
That worked, the package list loads in about 2 seconds now. So it's safe to assume that nuclide-installer
is the culprit. Still wondering if it's something that needs to be fixed only there or as well here. :confused:
I don't think it's directly a problem with nuclide-installer
as it only runs apm install
over the 13 packages required by nuclide.
Same problem for me. Installing with ./scripts/dev/setup
is perfect now, but i want the apm install nuclide-installer
.
Did you tried sudo apm install nuclide-installer
?
@thedaniel I suspect that Atom is making too many requests / UI updates when you have a large number of packages installed. When I run process._getActiveRequests()
, I see a ton of stuff in flight.
I think a batch API of some sort would help.
I have 174 packages installed and when opening the installed packages view I could actually make myself a coffee since it renders atom unusable for about a minute :smile:
Could also be related to this, maybe