🎩 What? Why?

Follow up for #8066 (see the related discussion in that issue).

This proposes a solution for the package.json override in the webpacker installation task (decidim:webpacker:install).

This is not ideal because it is very slow as it clones the whole Decidim git repository to node_modules.

This is, however, how it should be solved. What needs to be done after:

• Create a new NPM package that ships with the dependencies listed in Decidim's package.json
• Mark the devDependencies correctly to that file as all the dependencies are now listed within dependencies. The devDependencies are those NPM packages that are not necessarily relevant for the Decidim application (jest related, etc. see Configure webpacker additional paths and entry points programmatically #8066 (comment))
• Release that package to NPM, e.g. with name @decidim/essentials
• Replace the line system! "npm i decidim/decidim#develop" with system! "npm i @decidim/essentials"

📌 Related Issues

• Related to Migrate to Webpacker #7464, Migrate to Webpacker (CSS and images) #7733

Testing

Run the development app with the webpack-dev-server.

📋 Checklist

• ❓ CONSIDER adding a unit test if your PR resolves an issue.
• ✔️ DO check open PR's to avoid duplicates.
• ✔️ DO keep pull requests small so they can be easily reviewed.
• ✔️ DO build locally before pushing.
• ✔️ DO make sure tests pass.
• ✔️ DO make sure any new changes are documented in docs/.
• ✔️ DO add and modify seeds if necessary.
• ✔️ DO add CHANGELOG upgrade notes if required.
• ✔️ DO add to GraphQL API if there are new public fields.
• ✔️ DO add link to MetaDecidim if it's a new feature.
• ❌AVOID breaking the continuous integration build.
• ❌AVOID making significant changes to the overall architecture.