Change Varbase Editor requirements to follow with Drupal Libraries Management with Varbase Libraries

Problem/Motivation

• Issue #3541158: Switched from Asset Packagist to NPM/Yarn with drupal-libraries-sync for Varbase Libraries Management
  

  Varbase Libraries Management

  • The NPM/Yarn Method
  • Available Drupal Libraries Sync Commands
  • Adding New Libraries
  • Example
  • Removing No Longer Needed Libraries
  • Troubleshooting
  Migrating Existing Projects to NPM/YARN with drupal-libraries-sync
  The Composer Method (Deprecated)

Proposed resolution

• Change Varbase Editor requirements to follow with the new method with Varbase Libraries Management

Remaining tasks

• ✅ File an issue about this project
• ✅ Addition/Change/Update/Fix to this project
• ✅ Testing to ensure no regression
• ➖ Automated unit/functional testing coverage
• ➖ Developer Documentation support on feature change/addition
• ➖ User Guide Documentation support on feature change/addition
• ➖ UX/UI designer responsibilities
• ➖ Accessibility and Readability
• ✅ Code review from 1 Varbase core team member
• ✅ Full testing and approval
• ✅ Credit contributors
• ✅ Review with the product owner
• ✅ Update Release Notes and Update Helper on new feature change/addition
• ✅ Release varbase-10.1.0-beta1, varbase_editor-10.1.0-beta2, varbase-10.0.7, varbase_editor-10.0.16

Varbase update type

• ✅ No Update
• ➖ Optional Update
• ➖ Forced Update
• ➖ Forced Update if Unchanged

User interface changes

• N/A

API changes

• N/A

Data model changes

• N/A

Release notes snippet

• [#3544275] chore: Change Varbase Editor requirements to follow with Drupal Libraries Management with Varbase Libraries