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

Fix Development Warnings #351

Open
ThomasThelen opened this issue Jun 24, 2023 · 0 comments
Open

Fix Development Warnings #351

ThomasThelen opened this issue Jun 24, 2023 · 0 comments
Assignees
Labels
deployment Related to running, building, and infastructure
Milestone

Comments

@ThomasThelen
Copy link
Member

There are a few warnings related to our dependencies that we should take a look at

To Reproduce:

  1. Checkout
  2. npm i
  3. See warnings

Deprecations

There are a few instances of packages being moved to other modules. For example,

npm WARN deprecated [email protected]: This package has moved: use @turf/turf instead
Fixing this warning will resolve most of the issues and should probably be looked at first.

Security Warnings

There are four high priority issues; two can be auto-resolved by npm audit fix. The other two will require a closer look. The general idea is to use LTS over Stable npm versions and LTS over Active angular versions.

@ThomasThelen ThomasThelen added the deployment Related to running, building, and infastructure label Jun 24, 2023
@ThomasThelen ThomasThelen added this to the 2.0.3 milestone Jun 26, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
deployment Related to running, building, and infastructure
Projects
None yet
Development

No branches or pull requests

2 participants