Why do node installed workflows randomly reset all the time?

[nikivi]

I have a few workflows that I installed with npm. The issue with these workflows is that I often like to add an external trigger to the workflows I am using. However after a few days or weeks, the workflows randomly reset to their initial state, disregarding all my changes.

 

An example of a workflow that reset itself multiple times already is MDN. But there is many more.

 

Why does this happen? And can I avoid it?

Edited March 7, 2018 by nikivi

[deanishe]

Did you install them with npm? They're likely being rewritten by Alfy's installation/update mechanism.

[nikivi]

1 minute ago, deanishe said:

Did you install them with npm?

 

Yes I did. I guess there is no way to avoid it then. Oh well.

[deanishe]

1 minute ago, nikivi said:

I guess there is no way to avoid it then

 

Apart from, you know, not installing them with npm…

[nikivi]

1 minute ago, deanishe said:

Apart from, you know, not installing them with npm…

 

Will I get workflow updates this way? I am not too familiar with Alfy.

[nikivi]

Also in case of MDN, there is no .alfredworkflow file anywhere to be found. Only way I see how to install it is npm.

[nikivi]

I am currently 'solving' this issue for myself by automating insertion of the external triggers with same trigger name.

 

 

Which whilst a bit annoying, works. I will try to install things not from npm though going forward.

[deanishe]

1 minute ago, nikivi said:

Will I get workflow updates this way? I am not too familiar with Alfy.

 

Me neither, tbh. I've definitely seen Node-based workflows notify me of updates, and I never install them with npm, but I've no idea if they were based on Alfy…

 

In any case, however you update your workflows, you're going to lose the elements you've added. For your favourites, at least, it might be easier to manage your changes by forking the repo and handling updates with git instead of using workflows' or Alfred's own update mechanisms.