JavaScript Framework Updates Suck, How to Make Them Suck(less)

• Hapi

  50 14,509 7.0 JavaScript

  The Simple, Secure Framework Developers Trust

  

Lob found itself in a similar situation with hapi, an open-source NodeJS framework used to build powerful and scalable web applications. We were running version v16 when v17 was announced. The release notes refer to v17 as a new framework because it makes fundamental changes to how business logic is interfaced with the framework. The main change and the motivation for this release was replacing callbacks with a fully async/await interface. Though few would argue the advantages of this shift, the result was dozens upon dozens of breaking changes. At Lob, it meant hundreds, and our list of dependencies was long. The upgrade sat on the backburner and as 17 turned to 18, then 20, we realized it was time to git-er-done.

• hapi-rate-limiter

  1 17 0.0 JavaScript
  

Here's an example of updating an internal plugin from v16 to v17+ (this and this). We broke each update into multiple commits:

• SurveyJS

  surveyjs.io featured

  Open-Source JSON Form Builder to Create Dynamic Forms Right in Your App. With SurveyJS form UI libraries, you can build and style forms in a fully-integrated drag & drop form builder, render them in your JS app, and store form submission data in any backend, inc. PHP, ASP.NET Core, and Node.js.

  

Suggest a related project