With #234 we migrated the client packages to the @glsp npm org. As a consequence, the automatic deployment to npm as "next" packages no longer works and the CI build for the master branch does not complete and times out.
In addition, we should polish the script so that:
only packages that were effectively changed get deployed. Previous all client packages were deployed and published. This led to a lot of redundant versions. However, determining which packages have changed might be difficult for PRs with multiple commits. We should have a look at https://github.com/theia-ide/theia for this.
Internal dependencies between the packages should be declared with the exact version number (e.g. "0.2.0-next.029a5b81" instead of "next") to minimize potential resolution conflicts when consuming the "nightly" packages.
With #234 we migrated the client packages to the
@glspnpm org. As a consequence, the automatic deployment to npm as "next" packages no longer works and the CI build for the master branch does not complete and times out.In addition, we should polish the script so that:
only packages that were effectively changed get deployed. Previous all client packages were deployed and published. This led to a lot of redundant versions. However, determining which packages have changed might be difficult for PRs with multiple commits. We should have a look at https://github.com/theia-ide/theia for this.
Internal dependencies between the packages should be declared with the exact version number (e.g. "0.2.0-next.029a5b81" instead of "next") to minimize potential resolution conflicts when consuming the "nightly" packages.