Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update internal linting dependencies #1550

Merged
merged 2 commits into from Jan 31, 2021
Merged

Conversation

bmish
Copy link
Contributor

@bmish bmish commented Jan 26, 2021

Had to disable a few new eslint-plugin-node violations.

@@ -79,7 +79,7 @@ async function run( args, options ) {
require( filePath );
} catch ( e ) {
if ( e.code === "ERR_REQUIRE_ESM" && ( !nodeVint || nodeVint >= 72 ) ) {
await import( filePath );
await import( filePath ); // eslint-disable-line node/no-unsupported-features/es-syntax
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This rule sounds pretty severe, but looks like it is an upstream bug. This syntax is supported since Node 10. The actual functionality is supported (without experimental flag) since Node 12, but that is a run-time check. The syntax is safe to have (unused) on Node 10.

Disabling the rule here seems fine, since we are already covered from a syntax perspective by ESLint's built-in checks, and by the integration tests running on the various Node versions in Travis CI.

Ref mysticatea/eslint-plugin-node#250.

@Krinkle
Copy link
Member

Krinkle commented Jan 31, 2021

Confirmed locally that re-generating package-lock.json yields the exact same file (no diff).

@Krinkle Krinkle merged commit 84a7e87 into qunitjs:master Jan 31, 2021
@Krinkle
Copy link
Member

Krinkle commented Jan 31, 2021

Thanks @bmish !

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants