chore: removing unneeded files and folders that will be replaced

georgewrmarshall commented 1 week ago

Description

This PR resolves Issue #104 by removing the unneeded folders and files as part of the design tokens migration process. Following the Package Migration Process Guide

Manual testing steps

Verify that the files and folder mentioned in this step have been removed
Verify any other files and folders like storybook have been removed.

Pre-merge author checklist

[x] I've followed MetaMask Contributor Docs
[x] I've completed the PR template to the best of my ability.
[x] I’ve included tests if applicable.
[x] I’ve documented my code using JSDoc format if applicable.
[x] I’ve applied the appropriate labels to the PR.

Pre-merge reviewer checklist

[ ] I've manually tested the PR (e.g., pulled and built the branch, checked the app, and verified the updated tokens).
[ ] I confirm that this PR addresses all acceptance criteria described in issue #104 and includes necessary testing evidence such as recordings or screenshots.

socket-security[bot] commented 1 week ago

New and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Package	New capabilities	Transitives	Size	Publisher
npm/sass@1.80.7	filesystem, unsafe Transitive: environment, shell	`+19`	13.1 MB	hcatlin, nex3, sassbot
npm/tsup@7.3.0	environment, eval, filesystem Transitive: network, shell, unsafe	`+79`	514 MB	egoist

View full report↗︎

socket-security[bot] commented 1 week ago

🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎

To accept the risk, merge this PR and you will not be notified again.

Alert	Package	Note	Source	CI
Deprecated	npm/tsup@7.3.0	Reason: Breaking node 16	`merged-packages/design-tokens/package.json`	⚠︎

View full report↗︎

Next steps

What is a deprecated package?

The maintainer of the package marked it as deprecated. This could indicate that a single version should not be used, or that the package is no longer maintained and any new vulnerabilities will not be fixed.

Research the state of the package and determine if there are non-deprecated versions that can be used, or if it should be replaced with a new, supported solution.

Take a deeper look at the dependency

Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev.

Remove the package

If you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency.

Mark a package as acceptable risk

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of ecosystem/package-name@version specifiers. e.g. @SocketSecurity ignore npm/foo@1.0.0 or ignore all packages with @SocketSecurity ignore-all

@SocketSecurity ignore npm/tsup@7.3.0

MetaMask / metamask-design-system