V1 support for long term?

[kocv59]

V2 is not just a few breaking changes it's a totally different project. There are benefits but it's too different it should have been made as a different package in npm. The upgrade documentation is not clear and many issues here are troubled with it too.

Can V1 be relied on to get security fixes and keeping it working in future browsers versions in the long term so we can stay on it? I give up trying to upgrade it. If V1 isn't possible long term can someone recommend a simple alternative package?

[liesahead]

I agree, wasted a full day and it's not even close. Like getContainerData is stated as deprecated but there's no alternative suggested. Also, viewMode was just a simple convenient setting but now it's not stated clearly how to set up the same behavior, just stated to use css transform of several elements.

Not sure why library author decided to make second version so much more overcomplicated.

[limonte]

Not sure why library author decided to make second version so much more overcomplicated.

Isn't it what webdev is all about? Creating unnecessary complexity just for fun.

They work really hard to make things worse (c)

[kocv59]

@fengyuanchen Could you consider reintroducing support for Cropper's v1 syntax as an option in v2? The feedback on this issue has been overwhelmingly positive, indicating that many users are unhappy with the recent changes.

Looking at the npm statistics, only 17,000 out of 800,000 users have adopted v2 months after its release, which suggests a significant lack of acceptance.

Your apparent disregard for backward compatibility has led many who integrated this package into their projects to lose trust. Making such drastic changes without a clear upgrade path or adequate documentation is concerning. If the changes had improved the experience, it might be more acceptable, but they seem to have made things worse.

Is it really appropriate to experiment with a new syntax in a production package that serves nearly a million users? Please consider supporting v1 syntax again.

[fengyuanchen]

V1 is still available for all users. v2 is just an option.

[kocv59]

Will you support V1 as long as V2 and further versions? If not the forced upgrade to an inferior version is delayed only.