azurePublish should not use internal packages such as code-editor #5744
Labels
P1
Painful if we don't fix, won't block releasing
Team: Runtime & Publishing
Type: Bug
Something isn't working
Milestone
azurePublish or any other extensions (sitting under extensions directory) should not have knowledge about internal yarn workspace packages.
In this particular case, azurePublish wants to display a jsonEditor and should import monaco directly instead of depending on @bfc/code-editor. This causes an issue with node module discovery since it has no idea about yarn workspaces inside Composer directory it tries finding them on npm and fails.
The text was updated successfully, but these errors were encountered: