@fimbul/mithotyn - npm Package Versions

v0.24.0

:tada: This release contains two major features: caching and code fixes in the LanguageService plugin.

:warning: Breaking Changes:

The changes in the LanguageService plugin require that you update the @fimbul/mithotyn dependency and the fimbullinter.vscode-plugin VSCode plugin if you were using one of them.

Features:

• new rule: no-object-spread-of-iterable warns about spreading an array into an object
• new rule: no-implicit-tostring warns about implicit string coercion of certain types
• new CLI option: --cache enables caching for fast incremental linting. Read more about caching
• the LanguageService plugin uses caching to speed up linting in your editor
• the LanguageService plugin now provides fixes for fixable findings

v0.21.0

:warning: Breaking Changes:

• TypeScript v3.1 and v3.2 is no longer officially supported
• Node.js v6 is no longer supported
• Rule.supports can now return a string respresenting the reason for not supporting the file
• Linter#lintAndFix now requires a ProgramFactory instead of Program
• Linter#lintAndFix UpdateFileCallback is now expected to only return a SourceFile
• no-inferred-empty-object was renamed to no-uninferred-type-parameter

Features:

• rules now debuglog the reason for not supporting a certain file
• performance improvements
  • when linting with --project --references
    • parsed tsconfig.json files are cached for all project references
  • when linting with --project --fix
    • the project's dependency graph is recalculated lazily the next time a typed rule reuqests type information after fixing a file
    • module resolutions are cached between fixes
• no-uninferred-type-parameter properly handles new default constraint unknown
• no-uninferred-type-parameter now detects uninferred type parameters in JS code falling back to any
• no-uninferred-type-parameter correctly handles higher order function types
• no-useless-initializer checks array destructuring
• better handling of computed property names
• better handling of object and array destructuring assignments

Bugfixes:

• comments are now included in the transpiled code and declaration files, this makes JSDoc and deprecations visible to API consumers

v0.18.0

:warning: Breaking Changes:

• configuration: patterns (exclude and overrides[].files) match dotfiles, e.g. *.spec.ts now matches .foo.spec.ts.
• disable comments: handling of nested ranges changed. //wotan-enable-line in a line disabled by //wotan-disable-next-line is ignored
• API: completely refactored FileFilterFactory, FileFilter, LineSwitchFilterFactory, LineSwitchParser and DefaultLineSwitchParser

Features:

• unchecked JS files (//@ts-nocheck or checkJs: false) are never linted with type information
• added report-useless-directives CLI option to report unused and redundant enable and disable comments

Bugfixes:

• wotan: added missing exports to the public API
• patterns in configuration files match dotfiles (see breaking changes)

v0.17.0

:tada: This release introduces a plugin for TypeScript's LanguageService. This enables in-editor linting while you type. See the docs for more details.

:warning: Breaking Changes:

• TypeScript 2.8 and 2.9 is no longer supported
• API:
  • Failure was renamed to Finding throughout the codebase
  • Resolver adds a new required method getDefaultExtensions
  • Resolver#resolve makes parameters basedir and extensions optional
  • Runner requires a new service FileFilterFactory
  • added severity suggestion

Features:

• new package @fimbul/mithotyn provides in-editor linting through a TypeScript LanguageService Plugin
• new severity: suggestion
• --fix can no longer introduce syntax errors
• async-function-assignability: checks methods and properties with computed names
• async-function-assignability: checks method overloads individually
• new service abstraction FileFilterFactory and FileFilter allow customizing which files are linted
• @fimbul/ve no longer includes the line break after the opening tag in the linted code
• @fimbul/ve correctly adjusts the column of findings in the first line if there is no line break after the opening tag
• prefer-number-methods: fixed finding location

Bugfixes:

• declaration files no longer contain const enum
• core services no longer rely on the existence of require
• YAML configuration can now contain YAML-specific types