save on beautify refuses to fire unless manually done first about atom-beautify HOT 4 CLOSED

At first read it immediately struck me as an issue caused by using activation events (See 4271bfe ). However, if you say it just started happening within the last 24 hours then I am a little surprised.
I will look into this as soon as I can.

The activation events were so that the package would not load until initially called once (like you described), so therefore the load time is faster and offset to the time of the first beautify. However, this would of course mean that observers to events such as the save event would not be created until after that first beautify. So ideally, simply removing the activation event would solve this issue.

from atom-beautify.

That fixed it. Just removing the package.json item. Thanks!

Personally speaking it doesn't add "too much" startup time. That's me coming over from using webstorm as an IDE though.

"This package added 141ms to startup time."

You've done a great job with this!

from atom-beautify.

Excellent. Glad to hear it worked!
I will

• remove activationEvents.

And also in the future be doing some even more major refactoring and performance improvements. I believe I can keep the load time and general performance high while not using activationEvents and providing all of the functionality the users love.

Thanks for your feedback!

from atom-beautify.

Published v0.6.2 with fix :).

from atom-beautify.