Doesn't resolve promise if a package has deferred activation

[postcasio]

If a package you're trying to load has activationEvents defined in its package.json, activation will be deferred and the promise returned from atom.packages.activatePackage will never resolve.

I think this can be gotten around by calling package.activateNow() instead of activating through the package manager but I'm not sure if it'll work properly.

[abe33]

Actually, the promise will be resolved when all the packages have been activated, for instance, in the minimap-find-and-replace package that relies on find-and-replace that defines activation events, the promise is resolved when you toggle the find view. But yes, if one package is never activated the promise will never resolve.

Have you any issue with this? I mean, is there a specific situation where the fact that it waits for all packages to be activated is an issue for you?
I thought that, in most case, a package that relies on many other packages should not assume that all these packages will be available at start (that's why I wrote this helper in the first place).
Maybe there's a need for another helper that use activateNow instead?

[postcasio]

Oops, you're right. It will resolve eventually when the activation events are triggered.

What I wanted to do was use it for my error-status package to activate the bug-report package:

requirePackages('bug-report').then([bugReport]) -> bugReport.open ...

But since it has deferred activation, it would not resolve immediately. I decided to just trigger the bug-report:open event in the end which is a better solution anyway. I think a separate helper for forcing immediate activation could be helpful though.

[abe33]

I'll add something for this, I'll just need to make sure that I can access loaded but not activated packages (I remember a discussion about that on discuss).