The `yarn.lock` still contains the removed static plugins that were replaced by dynamic plugins
Zaperex opened this issue · comments
What needs to be done?
The yarn.lock still contains the removed static plugins that were removed and replaced by dynamic plugins in #631. This results in unused modules being created for them in the node_modules. We will need to fully remove them from the yarn.lock.
Ex: Ansible Automation Platform Backend plugin is still present in the yarn.lock
The yarn.lock contains them, because the wrappers of dynamic plugins are part of the monorepo structure.
However, when the backend application itself is build, these packages are not part of the dependencies anymore.
So when installing the production dependencies for the built backend (running install --frozen-lockfile --production based on the content of the targz result of the backend build), the imports mentioned in the dynamic plugin wrapper sub-projects are not installed inside the resulting node_modules.
So it seems to me that there's no real problem here.
Seems like the difference between development and production.
@Zaperex feel free to close the issue if this explanation makes sense for you.