Skip to content

test: ignore package-lock.json for eslint-webpack-plugin#19572

Merged
snitin315 merged 2 commits intomainfrom
fix-type-integration-tests
Mar 24, 2025
Merged

test: ignore package-lock.json for eslint-webpack-plugin#19572
snitin315 merged 2 commits intomainfrom
fix-type-integration-tests

Conversation

@fasttime
Copy link
Copy Markdown
Member

@fasttime fasttime commented Mar 24, 2025

Prerequisites checklist

What is the purpose of this pull request? (put an "X" next to an item)

[ ] Documentation update
[ ] Bug fix (template)
[ ] New rule (template)
[ ] Changes an existing rule (template)
[ ] Add autofix to a rule
[ ] Add a CLI option
[ ] Add something to the core
[X] Other, please explain: fix type integration tests

This PR fixes an error in type integration tests that has been occurring since the publishing of @types/estree@1.0.7, e.g.: https://github.com/eslint/eslint/actions/runs/14029899007/job/39275099400. The new version of @types/estree@1.0.7 adds a new required property to a type (see DefinitelyTyped/DefinitelyTyped#72206), and this results in an incompatibility with previous versions of the same package.

What changes did you make? (Give an overview)

Changed a command in a CI workflow so that eslint-webpack-plugin gets installed with the --no-package-lock flag in the type integration tests. This causes eslint-webpack-plugin to use the same version of @types/estree as ESLint does, i.e. the latest v1.0.7 instead of v1.0.6 specified in package-lock.json.

Is there anything you'd like reviewers to focus on?

Does this approach make sense?

@github-project-automation github-project-automation Bot moved this to Needs Triage in Triage Mar 24, 2025
@eslint-github-bot eslint-github-bot Bot added the chore This change is not user-facing label Mar 24, 2025
@fasttime fasttime marked this pull request as ready for review March 24, 2025 16:41
@fasttime fasttime requested a review from a team as a code owner March 24, 2025 16:41
run: |
npm install
npm install ../eslint
npm install --no-package-lock ../eslint
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Should we use --no-package-lock for other packages as well to avoid such future issues?

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

I've added --no-package-lock to the npm install command for neostandard as well. The repos for the other packages don't contain a package-lock.json file.

@netlify
Copy link
Copy Markdown

netlify Bot commented Mar 24, 2025

Deploy Preview for docs-eslint failed. Why did it fail? →

Name Link
🔨 Latest commit 1b14d48
🔍 Latest deploy log https://app.netlify.com/sites/docs-eslint/deploys/67e1878f4c8286000846aa12

@netlify
Copy link
Copy Markdown

netlify Bot commented Mar 24, 2025

Deploy Preview for docs-eslint canceled.

Name Link
🔨 Latest commit 47cca01
🔍 Latest deploy log https://app.netlify.com/sites/docs-eslint/deploys/67e18fce72a4f50008ee7cf6

Copy link
Copy Markdown
Contributor

@snitin315 snitin315 left a comment

Choose a reason for hiding this comment

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

LGTM, thanks!

@snitin315 snitin315 added the accepted There is consensus among the team that this change meets the criteria for inclusion label Mar 24, 2025
@snitin315 snitin315 moved this from Needs Triage to Implementing in Triage Mar 24, 2025
@snitin315 snitin315 merged commit 76064a6 into main Mar 24, 2025
29 of 30 checks passed
@snitin315 snitin315 deleted the fix-type-integration-tests branch March 24, 2025 17:13
@github-project-automation github-project-automation Bot moved this from Implementing to Complete in Triage Mar 24, 2025
@fasttime fasttime mentioned this pull request Oct 10, 2025
1 task
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

accepted There is consensus among the team that this change meets the criteria for inclusion chore This change is not user-facing github actions

Projects

Status: Complete

Development

Successfully merging this pull request may close these issues.

2 participants