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

Triage of necessary node modules #77

Open
hepplerj opened this issue Feb 2, 2022 · 2 comments
Open

Triage of necessary node modules #77

hepplerj opened this issue Feb 2, 2022 · 2 comments
Assignees
Labels
dependencies Pull requests that update a dependency file

Comments

@hepplerj
Copy link
Member

hepplerj commented Feb 2, 2022

I want to closely look through the current node modules in package.json and see what we can eliminate so we won't have to worry too much about dependency/security updates.

@hepplerj hepplerj added the dependencies Pull requests that update a dependency file label Feb 2, 2022
@hepplerj hepplerj self-assigned this Feb 2, 2022
@lmullen
Copy link
Member

lmullen commented Feb 3, 2022

That's a good idea. There are basically three categories of dependencies:

  • Visualizations
  • Stuff for Foundation
  • eslint

Maybe the Foundation stuff can go. They probably pull in the majority of other dependencies.

However, I think our security implications are low. We aren't running this JS server side.

@hepplerj
Copy link
Member Author

This should also include removing any lingering gulp files, etc.

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
Projects
None yet
Development

No branches or pull requests

2 participants