[MGNLFE-165] Process for frontend-helpers library maintainance  Created: 26/Jan/22  Updated: 25/Apr/23  Resolved: 13/Apr/22

Status: Closed
Project: Magnolia Frontend Helpers
Component/s: None
Affects Version/s: None
Fix Version/s: 1.2.2

Type: Story Priority: Major
Reporter: Christopher Zimmermann Assignee: Jaroslav Simak
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File Screenshot 2022-03-29 at 18.38.04.png     PNG File Screenshot 2022-03-29 at 18.45.52.png    
Issue Links:
Relates
relates to MGNLFE-136 Get rid or update deprecated Angular ... Closed
dependency
depends upon MGNLFE-164 Standardize frontend-helpers sample p... Closed
is depended upon by MGNLCE-281 INT tests SPA components Closed
is depended upon by MGNLCE-283 INT tests ext.SPA components Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Date of First Response:
Epic Link: SaaS TPR - SPA Tests
Sprint: DevX 5, DevX 6, DevX 7
Story Points: 3
Team: DeveloperX

 Description   

Problem

The frontend-helpers libraries themselves, and their sample projects require constant maintenance over time due to their dependencies being updated. 2 key things are happening:

  • The key framework libraries are evolving - ie React, Angular, Vue and thier CLIs. Our editor libraries and sample projects need to stay modern and reflect the changing usaages of these libraries. 
  • Vulnerabilities are detected in dependencies. When you compile the libraries or the samples you get security warnings. These can scare customers and could potentially introduce real security problems.

Therefore - Create procesess to ensure that

  • frontend-helpers are up to date with latest React, Vue, Angular libraries.
  • demo projects to latest React, Vue, Angular library versions & latest frontend-helper versions.
  • remove deprecaated dependencies and 'npm install warnings' in frontend-helpers and demo projects.
  • (Could these processes also be used on the "minimal-headless-spa-demos"?

For example we could commit to update our code within 3 months of new major dependency update (like React)

Note

This could be achieved as a part of the release process.

In that case we could include these in a checklist on the release documentation wiki page.

? Make the builds fail where there are vulnerabilities
 

Angular 10 is no longer supported

https://angular.io/guide/releases


Generated at Mon Feb 12 05:44:52 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.