Problem Description

Yarn/npm/yarn builds differ significantly from upstream, this means changes have to be cherry-picked or manually fixed each time.

External fetches have been a reoccurring issue, some changes cannot be pushed upstream as they divulge sensitive internal information such as hostnames.

Proposed Solution

• Make configuration changes injectable (Using exclusively the config files seems to fix most frontend-maven-plugin issues)
• Have prod specific package.json tasks (minimal, removing steps like Snyk)
• Correct node version configuration (eg. no need to specify npm version anymore)

DoD

• Components that have yarn/npm build steps no longer need manual intervention to build