myapp/node_modules/eslint-module-utils/CHANGELOG.md

Change Log

All notable changes to this module will be documented in this file. This project adheres to Semantic Versioning. This change log adheres to standards from Keep a CHANGELOG.

Unreleased

v2.6.0 - 2020-03-28

Added

[New] Print more helpful info if parsing fails (#1671, thanks @kaiyoma)

v2.5.2 - 2020-01-12

Fixed

• Makes the loader resolution more tolerant (#1606, thanks @arcanis)
• Use createRequire instead of createRequireFromPath if available (#1602, thanks @iamnapo)

v2.5.1 - 2020-01-11

Fixed

• Uses createRequireFromPath to resolve loaders (#1591, thanks @arcanis)
• report the error stack on a resolution error (#599, thanks @sompylasar)

v2.5.0 - 2019-12-07

Added

• support parseForESLint from custom parser (#1435, thanks @JounQin)

Changed

• Avoid superfluous calls and code (#1551, thanks @brettz9)

v2.4.1 - 2019-07-19

Fixed

• Improve parse perf when using @typescript-eslint/parser (#1409, thanks @bradzacher)
• Improve support for TypeScript declare structures (#1356, thanks @christophercurrie)

v2.4.0 - 2019-04-13

Added

• no-useless-path-segments: Add noUselessIndex option (#1290, thanks @timkraut)

Fixed

• Fix overwriting of dynamic import() CallExpression ([no-cycle], [no-relative-parent-import], [no-unresolved], [no-useless-path-segments]) (#1218, #1166, #1035, thanks @vikr01)

v2.3.0 - 2019-01-22

Fixed

• use process.hrtime() for cache dates (#1160, thanks @hulkish)

v2.2.0 - 2018-03-29

Changed

• parse: attach node locations by default.
• moduleVisitor: visitor now gets the full import statement node as a second argument, so rules may report against the full statement / require call instead of only the string literal node.

v2.1.1 - 2017-06-22

Re-releasing v2.1.0 after vetting (again) and unable to reproduce issue.

v2.1.0 - 2017-06-02 [YANKED]

Yanked due to critical issue with cache key resulting from #839.

Added

• parse now additionally passes filePath to parser in parserOptions like eslint core does

v2.0.0 - 2016-11-07

Changed

• unambiguous no longer exposes fast test regex

Fixed

• unambiguous.test() regex is now properly in multiline mode