-
Story
-
Resolution: Fixed
-
Major
-
None
-
None
-
None
-
-
Empty show more show less
-
DevX 5, DevX 6, DevX 7
-
3
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
- depends upon
-
MGNLFE-164 Standardize frontend-helpers sample projects
- Closed
- is depended upon by
-
MGNLCE-281 INT tests SPA components
- Closed
-
MGNLCE-283 INT tests ext.SPA components
- Closed
- relates to
-
MGNLFE-136 Get rid or update deprecated Angular devDependencies
- Closed