depcheck action workflow

[prishavall]

Github Issue: #869

We have instances where we install a frontend library with yarn, but then we don't actually end up using it in our code. We should try to keep our frontend package size as small as possible and keep only the essentials to make our builds run faster

It provides a new command npx dep-check to see if there are any unused dependencies

Testing Methodology
Ran it through the front-end directory

[sweep-ai]

Apply Sweep Rules to your PR?

• Apply: All new business logic should have corresponding unit tests.
• Apply: Refactor large functions to be more modular.
• Apply: Add docstrings to all functions and file headers.

[karkir0003]

left a comment

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
0.0% Duplication

[karkir0003]

@farisdurrani are the package.json files correctly updated? @prishavall needed to add depcheck as a dev dependency?

[farisdurrani]

Yes, it's more apt to put in devDep since it's not a critical functionality for the app

[karkir0003]

@dwu359 @farisdurrani added another comment

[sonarqubecloud]

Quality Gate passed

Kudos, no new issues were introduced!

0 New issues
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarCloud

[karkir0003]

LGTM! Good job on this :)

[farisdurrani]

Lgtm