		{
		"name": "@fimbul/mimir",
		"version": "0.6.0-dev.20180320",
		"version": "0.6.0-dev.20180321",
		"description": "Core rules of the Fimbullinter project",
		@@ -28,3 +28,3 @@ "main": "recommended.yaml",
		"dependencies": {
		"@fimbul/ymir": "0.4.0",
		"@fimbul/ymir": "0.6.0-dev.20180321",
		"chalk": "^2.3.2",
		@@ -31,0 +31,0 @@ "debug": "^3.1.0",

README.md

		@@ -31,2 +31,4 @@ # Mímir
		`no-inferred-empty-object` \| Warns if a type parameter is inferred as `{}` because the compiler cannot find any inference site. \| Really checks every type parameter of function, method and constructor calls. Correctly handles type parameters from JSDoc comments. Recognises type parameter defaults on all merged declarations.
		`no-misused-generics` \| Detects generic type parameters that cannot be inferred from the functions parameters. \| There's no similar TSLint rule.
		`no-nan-compare` \| Don't compare with `NaN`, use `isNaN(number)` or `Number.isNaN(number)` instead. \| Performance!
		`no-return-await` \| Warns for unnecesary `return await foo;` when you can simply `return foo;` \| The same as TSLint's rule. I wrote both, but this one is faster.
		@@ -38,3 +40,2 @@ `no-unreachable-code` \| Warns about statements that will never be executed. Works like TypeScript's dead code detection but doesn't fail compilation because it's a lint error. \| TSLint removed their `no-unreachable` rule in v4.0.0.
		`no-unused-label` \| Warns about labels that are never used or at the wrong position. \| TSLint only has `label-position` which doesn't check for unused labels.
		`no-nan-compare` \| Don't compare with `NaN`, use `isNaN(number)` or `Number.isNaN(number)` instead. \| Performance!
		`no-useless-assertion` \| Detects type assertions that don't change the type or are not necessary in the first place. requires type information \| TSLint's `no-unnecessary-type-assertion` does not detect assertions needed to silence the compiler warning `Variable ... is used before being assigned.` The Wotan builtin rule also checks whether the assertion is necessary at all or the receiver accepts the original type.
		@@ -41,0 +42,0 @@ `no-useless-initializer` \| Detects unnecessary initialization with `undefined`. \| TSLint's rule `no-unnecessary-initializer` doesn't fix all parameter initializers and gives false positives for destructuring.

recommended.yaml

Sorry, the diff of this file is not supported yet

		@@ -31,2 +31,4 @@ # Mímir
		`no-inferred-empty-object` \| Warns if a type parameter is inferred as `{}` because the compiler cannot find any inference site. \| Really checks every type parameter of function, method and constructor calls. Correctly handles type parameters from JSDoc comments. Recognises type parameter defaults on all merged declarations.
		`no-misused-generics` \| Detects generic type parameters that cannot be inferred from the functions parameters. \| There's no similar TSLint rule.
		`no-nan-compare` \| Don't compare with `NaN`, use `isNaN(number)` or `Number.isNaN(number)` instead. \| Performance!
		`no-return-await` \| Warns for unnecesary `return await foo;` when you can simply `return foo;` \| The same as TSLint's rule. I wrote both, but this one is faster.
		@@ -38,3 +40,2 @@ `no-unreachable-code` \| Warns about statements that will never be executed. Works like TypeScript's dead code detection but doesn't fail compilation because it's a lint error. \| TSLint removed their `no-unreachable` rule in v4.0.0.
		`no-unused-label` \| Warns about labels that are never used or at the wrong position. \| TSLint only has `label-position` which doesn't check for unused labels.
		`no-nan-compare` \| Don't compare with `NaN`, use `isNaN(number)` or `Number.isNaN(number)` instead. \| Performance!
		`no-useless-assertion` \| Detects type assertions that don't change the type or are not necessary in the first place. requires type information \| TSLint's `no-unnecessary-type-assertion` does not detect assertions needed to silence the compiler warning `Variable ... is used before being assigned.` The Wotan builtin rule also checks whether the assertion is necessary at all or the receiver accepts the original type.
		@@ -41,0 +42,0 @@ `no-useless-initializer` \| Detects unnecessary initialization with `undefined`. \| TSLint's rule `no-unnecessary-initializer` doesn't fix all parameter initializers and gives false positives for destructuring.

@fimbul/mimir - npm Package Compare versions

Improved metrics

Dependency changes