You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The classic Yarn used by ABP has been deprecated since 2020 and they recommending finding other alternatives but it is still used by ABP. Even if you can use other package managers yourself, I believe that ABP Suite etc are still using Yarn no matter what which will result in multiple lock-files etc. I also believe that today the advantages of using Yarn over NPM is not as great as they used to be, although I must admit to not being very up to date on this. It should probably be considered to either upgrade to current Yarn or use something else like NPM.
Is there an existing issue for this?
Description
Not a bug but a suggestion for improvement.
The classic Yarn used by ABP has been deprecated since 2020 and they recommending finding other alternatives but it is still used by ABP. Even if you can use other package managers yourself, I believe that ABP Suite etc are still using Yarn no matter what which will result in multiple lock-files etc. I also believe that today the advantages of using Yarn over NPM is not as great as they used to be, although I must admit to not being very up to date on this. It should probably be considered to either upgrade to current Yarn or use something else like NPM.
https://classic.yarnpkg.com/en/
The text was updated successfully, but these errors were encountered: