Add task analyze (use source-map-explorer)

[tokland]

Add task to analyze the build size of the package

📝 Implementation

• Add package source-map-explorer
• Add task "analyze"

🔥 Notes for the reviewer

Example for HTML output (a page will be open in a browser)::

$ yarn analyze

Example for TSV output:

$ yarn analyze --tsv |& grep node_modules | head -n10
../node_modules/exceljs/dist/exceljs.min.js	1165355
../node_modules/@eyeseetea/d2-api/2.36/schemas.js	415692
../node_modules/xlsx/xlsx.mjs	328005
../node_modules/react-dom/cjs/react-dom.production.min.js	118664
../node_modules/lodash/lodash.js	71604
../node_modules/@eyeseetea/d2-ui-components/node_modules/lodash/lodash.js	71403
../node_modules/lodash/lodash.min.js	70900
../node_modules/@eyeseetea/feedback-component/node_modules/moment/moment.js	60318
../node_modules/moment/moment.js	60229
../node_modules/@eyeseetea/d2-api/node_modules/iconv-lite/encodings/sbcs-data-generated.js	57519

From here we can start an analysis of the packages, for example:

24c354c1 (Eduardo Peredo Rivero 2023-07-28 12:21:07 -0500  36)         "exceljs": "4.3.0",
247f3c3d (Eduardo Peredo Rivero 2024-02-10 15:55:56 -0500  57)         "xlsx": "^0.18.5"

The schemas thing with d2-api is a known problem, but we've had no time to see how to solve it.

[tokland]

• Move xlsx to devDependencies (as it's only used for a script):

5,9M data-management-app.zip -> 5,4M data-management-app.zip

• Test script
• Test zip app (download data, download MER)