Project framework component updater bugs

The component updater is still a bit buggy.

For example, I just resumed working on my windows machine after 1-2 months.
It told me there are 6 updates image

However when checking the differences, most of them don’t have any changes:

In this case only the dmxDataTraversal.js has changes

The others don’t:


Because of this, I tend to just click ‘cancel’ whenever starting wappler these days and it tells me there are updates avail. But this way I’ll miss out on bug fixes like for the datatraversal.js

I belive this issue might be caused by line endings:
https://www.cs.toronto.edu/~krueger/csc209h/tut/line-endings.html
https://docs.github.com/en/get-started/getting-started-with-git/configuring-git-to-handle-line-endings

The hint came from the fact you use a mixture of Linux and Windows

If there were no changes to the files, those wouldn’t be in Git’s staging area in first place

2 Likes

Oh interesting, if that’s true I’ll just ignore this

It shouldn’t appear many times to update. Can you see how it goes from now on?

1 Like

This is now improved in the latest Wappler 6.2

1 Like

This topic was automatically closed after 20 hours. New replies are no longer allowed.