Enforce local yarn workspaces reference and avoid npm confusion
Description
Use local workspace package when referencing them
yarn 3 migration
package.json simplification
Use proper key name for workspace prefix
Fix Jest issues and previously silenced not build issues
Motivation and Context
Avoid npm confusion to always favor local workspaces
How Has This Been Tested?
If the workspaces are not built, launching a service that refer to it won't be possible, it won't try to download it from the public registry.
yarn workspaces has been favored rather than nx for the main scrips entry point (build:all, test:all, lint:all)
Screenshots (if appropriate):
Types of changes
[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ x] Breaking change (fix or feature that would cause existing functionality to change)
Checklist:
[ x] My code follows the code style of this project.
[ x] My change requires a change to the documentation.
[ x] I have updated the documentation accordingly.
Enforce local yarn workspaces reference and avoid npm confusion
Description
Use local workspace package when referencing them yarn 3 migration package.json simplification Use proper key name for workspace prefix Fix Jest issues and previously silenced not build issues
Motivation and Context
Avoid npm confusion to always favor local workspaces
How Has This Been Tested?
If the workspaces are not built, launching a service that refer to it won't be possible, it won't try to download it from the public registry. yarn workspaces has been favored rather than nx for the main scrips entry point (build:all, test:all, lint:all)
Screenshots (if appropriate):
Types of changes
Checklist: