Socket
Socket
Sign inDemoInstall

eslint-config-xo-typescript

Package Overview
Dependencies
Maintainers
1
Versions
80
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

eslint-config-xo-typescript - npm Package Compare versions

Comparing version 0.41.1 to 0.42.0

14

index.js

@@ -107,3 +107,3 @@ 'use strict';

'error',
'never'
'always-multiline'
],

@@ -371,3 +371,7 @@ 'comma-spacing': 'off',

'@typescript-eslint/no-non-null-asserted-optional-chain': 'error',
'@typescript-eslint/no-non-null-assertion': 'error',
// Disabled for now. There are just too many places where you need to use it because of incorrect types, for example, the Node.js types.
// TODO: Try to enable this again in 2023.
// '@typescript-eslint/no-non-null-assertion': 'error',
'no-redeclare': 'off',

@@ -400,3 +404,7 @@ '@typescript-eslint/no-redeclare': 'error',

'@typescript-eslint/no-unnecessary-type-constraint': 'error',
'@typescript-eslint/no-unsafe-argument': 'error',
// Disabled for now. When using try/catch, the error is by default `any` and if you pass the error anywhere, it will trigger this rule. This is a very common occurence.
// TODO: Enable this rule when TypeScript has more strongly typed errors, probably 2023 at the earliest.
// '@typescript-eslint/no-unsafe-argument': 'error',
'@typescript-eslint/no-unsafe-assignment': 'error',

@@ -403,0 +411,0 @@ '@typescript-eslint/no-unsafe-call': 'error',

{
"name": "eslint-config-xo-typescript",
"version": "0.41.1",
"version": "0.42.0",
"description": "ESLint shareable config for TypeScript to be used with eslint-config-xo",

@@ -5,0 +5,0 @@ "license": "MIT",

SocketSocket SOC 2 Logo

Product

  • Package Alerts
  • Integrations
  • Docs
  • Pricing
  • FAQ
  • Roadmap
  • Changelog

Packages

npm

Stay in touch

Get open source security insights delivered straight into your inbox.


  • Terms
  • Privacy
  • Security

Made with ⚡️ by Socket Inc