Skip to content
This repository has been archived by the owner on Oct 8, 2024. It is now read-only.

Upgrade linters and include config in npm package #152

Merged
merged 2 commits into from
Aug 1, 2024
Merged

Conversation

mattjohnsonpint
Copy link
Member

@mattjohnsonpint mattjohnsonpint commented Aug 1, 2024

Finally, typescript-eslint v8 has been released, the main feature being compatible with eslint v9.
https://typescript-eslint.io/blog/announcing-typescript-eslint-v8

Upgrading both.

This also adds the assemblyscript linter config to our npm package, for re-use by Hypermode plugins.

@mattjohnsonpint mattjohnsonpint requested a review from a team as a code owner August 1, 2024 19:59
Copy link

🚨 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 NoteSourceCI
Floating dependency npm/@types/eslint__js@8.42.3 🚫
Unpopular package npm/@assemblyscript/wasi-shim@0.1.0 🚫
Unpopular package npm/xid-ts@1.1.0 🚫
Floating dependency npm/@types/eslint@9.6.0 🚫
Floating dependency npm/@types/eslint@9.6.0 🚫

View full report↗︎

Next steps

What are floating dependencies?

Package has a dependency with a floating version range. This can cause issues if the dependency publishes a new major version.

Packages should specify properly semver ranges to avoid version conflicts.

What are unpopular packages?

This package is not very popular.

Unpopular packages may have less maintenance and contain other problems.

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/@types/eslint__js@8.42.3
  • @SocketSecurity ignore npm/@assemblyscript/wasi-shim@0.1.0
  • @SocketSecurity ignore npm/xid-ts@1.1.0
  • @SocketSecurity ignore npm/@types/eslint@9.6.0

@mattjohnsonpint mattjohnsonpint merged commit 35481a5 into main Aug 1, 2024
22 of 23 checks passed
@mattjohnsonpint mattjohnsonpint deleted the mjp/eslint branch August 1, 2024 20:15
@mattjohnsonpint mattjohnsonpint changed the title Update eslint Upgrade linters and include config in npm package Aug 1, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants