(Ab)using build profiles

[Jérémy Lal <kapouer@melix.org>]

To help tracking lots of dependencies in package.json, with how debian/control

dependencies are decided, I've started using build profiles to add some inline

metadata.

Bad idea ? Good idea ?

 , node-codemirror-lang-json
 , node-codemirror-lang-yaml <pkg.source.mut>
 , node-monaco-editor <pkg.source.replaced_by_codemirror>
 , node-monaco-editor-webpack-plugin <pkg.source.replaced_by_codemirror>
 , node-monaco-yaml <pkg.source.replaced_by_codemirror-lang-yaml>
 , node-util
 , node-os-browserify
 , node-p-limit
 , node-path-browserify
 , node-pino <pkg.source.useless>
 , node-react
 , node-react-dom
 , node-react-i18next <pkg.source.mut>
 , node-react-json-chart-builder <pkg.source.mut>
 , node-react-use-websocket <pkg.source.mut>
 , node-rollup
 , node-rrule <pkg.source.mut>
 , node-tslib <pkg.source.depof_node-rrule>
 , node-selfsigned <pkg.source.mut>

etc...

Jérémy