[Snyk] Upgrade tslint-to-eslint-config from 0.2.11 to 0.7.1 #41

snyk-bot · 2020-11-06T23:25:29Z

Snyk has created this PR to upgrade tslint-to-eslint-config from 0.2.11 to 0.7.1.

✨ Snyk has automatically assigned this pull request, set who gets assigned.
ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

The recommended version is 8 versions ahead of your current version.
The recommended version was released 6 months ago, on 2020-04-27.

The recommended version fixes:

Severity	Issue	PriorityScore (*)	Exploit Maturity
	Prototype Pollution SNYK-JS-MINIMIST-559764	387/1000 Why? Proof of Concept exploit, CVSS 5.6	Proof of Concept

(*) Note that the real score may have changed since the PR was raised.

Release notes

Package name: tslint-to-eslint-config

0.7.1 - 2020-04-27
This patch release, hot off the press from 0.7.0, comes with a new rule converter and more intelligent package install commands. Previous versions would suggest installing all new packages related to ESLint and/or typescript-eslint. This release will only suggest packages that don't exist in your package.json.

The full list of released PRs is:
- Add one-line rule converter #413
- Removed already-installed packages from install command #424
Thanks as usual to this release's dedicated external contributor, @KingDarBoja!
0.7.0 - 2020-04-26
This v0.7.0 brings us much closer to completing the 1.0 milestone. It's got a few converter and merger fixes along with a hefty dose of CLI output improvements. The CLI output is now more consistent from area-to-area and keeps detailed log output to the generated ./tslint-to-eslint-config.log. It'll also be more aggressive in asking to install packages if it fails to read from existing configuration files due to a package not being installed.

Additionally, a new --prettier flag will now indicate to include eslint-config-prettier in generated rulesets. It's enabled by default if no formatting rules already exist; otherwise, the CLI will strongly recommend using it.

The full list of changes is:
- #368: Support a converter for no-reference-import rule
- #385: Add merger for @typescript-eslint/consistent-type-assertions
- #386: Adjusted comment-format's check-space output for markers
- #405: Used package install command for list of required ESLint-related packages
- #408: Standardized outputs: CLI summaries, log details
- #409: Added tslint-eslint-plugin package as necessary to install commands
- #412: Added recommended --prettier flag to include eslint-config-prettier
- #418: Corrected 'tslint-eslint-plugin' to be 'eslint-plugin-tslint'
- #419: Intentionally fail fast on module lookup failures
- #420: Added basic @typescript-eslint/triple-slash-reference merger
Thanks as always to our great contributors!
0.6.0 - 2020-04-20
This new minor version release adds an FAQ notice explaining the generated ESLint file, which starts this project's journey towards better documenting best practices for generated configurations. Hooray!

In total, it contains:
- #238: [Feature] Add jsdoc-format converter
- #337: Add no-boolean-literal-compare converter
- #347: Fix arrow-parens converter
- #348: Added usage and base configuration FAQs
- #351: chore: set minimum node version to 10
- #353: Respect the original TSLint configuration of ban-types
Many thanks to our community contributors!
0.5.1 - 2020-02-10
This release improves the phrasing for unknown TSLint rules by shifting the blame to this repository instead of ESLint. It also contains a new converter for import-blacklist, a couple of small bugfixes, and a few development improvements.

The user-facing changes are:
- #277: Missing converter: import-blacklist to no-restricted-imports
- #299: "do not have an ESLint equivalent" is misleading
- #310: prefer-readonly: within @typescript-eslint
- #314: Convert space-within-parens to space-in-parens
Many thanks to our excellent contributors: @mc-suchecki, @adamazing, and @beenotung!
0.5.0 - 2019-12-24
This release contains several rule fixes as well as improvements around CLI output reporting:
- #276: Account for TSLint and @typescript-eslint rulesets
- #291: fix no-underscore-dangle
- #293: fix space-before-function-paren
- #297: Fix comment-format (capitalized-comments)
- #304: Stopped erroring when .vscode/settings.json doesn't exist
- #305: Improved spacing around reporting line groups
Eternal thanks to this release's repeat contributor, @bouzuya! ✨
0.4.0 - 2019-12-17
This fast v0.4.0 is a doozy! In addition to a selection of traditional converter and merger improvements, a new --editor option will convert your editor settings from the TSLint extension's to the ESLint extension's. 🚀
- #281: Fixed @typescript-eslint/member-delimiter-style and padding-line-between-statements converters
- #282: Add no-redundant-jsdoc converter
- #284: Missing merger [member-delimiter-style]
- #273: Generating space-before-function-paren
- #250: Convert editor settings
- #271: no-import-side-effect output rule
0.3.1 - 2019-11-16
This mini-release contains:
- Corrected no-import-side-effect output rule (#271)
0.3.0 - 2019-11-16
Most notably, this release lowers the minimum Node verison to 8 as hinted to in a few issues.

Many thanks the sole contributor this release:
- @deerawan
...for contributing:
- #242: Add converter trailing-comma
0.2.11 - 2019-10-29
Read more