The sync command forces all packages to be of the same version for a given npm package. If I update the got library in teraslice, it forces the update to all other packages in the monorepo to have the same version. This is problematic as teraslice is an esm based library now, but I cant use the esm only version of the package because not all the monorepo libraries are esm. This make it so that we cannot get rid of the dynamic import hack with got in the api section in teraslice until all packages are esm.
It seems to me this behaviour was meant to be a safety check to make sure all libraries run the same code as we have had problems in the past with out of sync code. However this is a problem when we intentionally need different things for different environments.
This is a note to fix the api issue when scripts and other packages are finally converted to esm modules
The sync command forces all packages to be of the same version for a given npm package. If I update the
gotlibrary in teraslice, it forces the update to all other packages in the monorepo to have the same version. This is problematic as teraslice is an esm based library now, but I cant use the esm only version of the package because not all the monorepo libraries are esm. This make it so that we cannot get rid of the dynamic import hack with got in the api section in teraslice until all packages are esm.It seems to me this behaviour was meant to be a safety check to make sure all libraries run the same code as we have had problems in the past with out of sync code. However this is a problem when we intentionally need different things for different environments.
This is a note to fix the api issue when scripts and other packages are finally converted to esm modules