Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unused NPM dependencies #4184

Closed
Crashillo opened this issue Dec 12, 2023 · 0 comments · Fixed by #4242
Closed

Unused NPM dependencies #4184

Crashillo opened this issue Dec 12, 2023 · 0 comments · Fixed by #4242
Labels
dependencies Pull requests that update a dependency file enhancement

Comments

@Crashillo
Copy link
Member

After running https://www.npmjs.com/package/depcheck, it point several libraries to presume be unused.
The current package.json is quite unsorted, leading to a harder identification of the core libraries from the negligible ones, the issue here is about identify if they can be safely removed or not.

In order to proceed:

  1. Sort the package.json to distinguish the application libraries from the development libraries (as these ones are always safely upgradable)
  2. Run yarn upgrade-interactive to update dependencies to the most up-to-date safe version
  3. Run yarn upgrade-interactive --latest to force update some dependencies, as long as they can continue working.
  4. Remove those dependencies, aimed by depcheck. This is delicate, and require to proceed one by one.
@Crashillo Crashillo added enhancement dependencies Pull requests that update a dependency file labels Dec 12, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file enhancement
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant