The current setup of the metamask-design-system follows the MetaMask module template used for a polyrepo structure. We need to update the repository to use a monorepo architecture, leveraging Yarn workspaces. The updated setup should be aligned with the structure used in MetaMask core. Unnecessary files should be removed, and the monorepo setup should follow the approach demonstrated in the POC shared-ui-monorepo.
Technical Details
Convert the current metamask-design-system repository from a polyrepo to a monorepo architecture.
Set up Yarn workspaces to manage packages within the monorepo.
Use the MetaMask core monorepo as inspiration for the structure and organization of the repository.
Move or remove any files that are unnecessary in the new monorepo setup.
Ensure the repository setup is consistent with the POC work done in the shared-ui-monorepo.
Update any scripts, configurations, or CI/CD pipelines to support the new monorepo structure.
Acceptance Criteria
The repository is successfully migrated to a monorepo architecture using Yarn workspaces.
Unnecessary files are removed, and the repository is cleaned up.
The setup follows the organization and best practices from MetaMask core and the shared-ui-monorepo POC.
CI/CD workflows and other automation scripts are updated to work with the new monorepo structure.
Stakeholders can review the updated repository setup.
Description
The current setup of the
metamask-design-systemfollows the MetaMask module template used for a polyrepo structure. We need to update the repository to use a monorepo architecture, leveraging Yarn workspaces. The updated setup should be aligned with the structure used in MetaMask core. Unnecessary files should be removed, and the monorepo setup should follow the approach demonstrated in the POC shared-ui-monorepo.Technical Details
metamask-design-systemrepository from a polyrepo to a monorepo architecture.Acceptance Criteria
References