Spike: migrate Bower to Webpack

Description

Background

Currently Bower is not the recommended way of loading assets any more. And the SpBowerBundle is deprecated/abandoned. Symfony 4 supports the use of Webpack.

The following documentation is affected:
http://www.integratedfordevelopers.com/content/documentation/article/loading-assets-with-bower
http://www.integratedfordevelopers.com/content/documentation/article/including-assets

Requirements

  • Set up a plan for the use of Webpack in Integrated

  • Create a list with things, files, documentation, etc. which have to be changed

Please note

  • The AssetBundle has been created to avoid loading all javascripts on every page. For example: a popup calendar is used only on one page in Integrated, we don't want to have this scripts loaded on every page. Migration of the Integrated AssetBundle is also part of this issue. The Assetbundle should work the same after the update to Webpack.

  • A problem of the current Bower setup is that a bower package may include php files, which will be placed in the web root. If you are not aware, this can introduce a security leak. Hopefully this is better with Webpack.

  • A problem of the current Bower setup is that a deletion or privatization of a repository ruins a deployment. Hopefully this is better with Webpack.

Environment

None

Deployment actions

None

Technical tasks

None

Status

Assignee

Unassigned

Reporter

Gerben Bosch

Client

Integrated Marijn

External issue ID

None

Follow up date

None

Code reviewer

None

Developer

None

Plan date

None

Max. hours

None

Error message

None

Min. hours

None

Product owner

Integrated Marijn

Refiner

None

Switches

None

Dev hour estimate

None

Story Points

5

Time tracking

21h 15m

Epic Link

Sprint

None

Fix versions

Priority

Major
Configure