Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

fix(types): add 2026/17 to EcmaVersion#11304

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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Merged

Conversation

DavidArchibald
Copy link
Contributor

@DavidArchibaldDavidArchibald commentedJun 13, 2025
edited by bradzacher
Loading

PR Checklist

Overview

I didn't open an issue because it's just for updating a single type for 2026.

I was happening to be manually updating my dependencies and was very confused when I suddenly started getting this error:

Argumentoftype 'Config<RulesRecord>' is not assignable to parameter of type 'InfiniteDepthConfigWithExtends'.Type'Config<RulesRecord>'isnotassignabletotype'ConfigWithExtends'.Typesofproperty'languageOptions'areincompatible.Type'import("/home/david/Projects/My Price Health/mono/node_modules/eslint/lib/types/index").Linter.LanguageOptions | undefined'isnotassignabletotype'import("/home/david/Projects/My Price Health/mono/node_modules/@typescript-eslint/utils/dist/ts-eslint/Config").FlatConfig.LanguageOptions | undefined'.Type 'import("/home/david/Projects/My Price Health/mono/node_modules/eslint/lib/types/index").Linter.LanguageOptions' is not assignable to type 'import("/home/david/Projects/My Price Health/mono/node_modules/@typescript-eslint/utils/dist/ts-eslint/Config").FlatConfig.LanguageOptions'.Typesofproperty 'ecmaVersion'areincompatible.Type'EcmaVersion | undefined'isnotassignabletotype'EcmaVersion'.Type'17'isnotassignabletotype'EcmaVersion'.

This happened because I was writing this:

exportdefaultts.config([...],    ...compat.extends("old-config")[...]);

Playground
Note to future readers: if you enter this playground after this PR has been merged the error will have been fixed because I don't know how to pin dependency version in the TypeScript playground

And due tocompat.extends simply returningConfig<RulesRecord>, the update inv9.29.0 to add support for 2026 broke this.

I also considered switching form manually definingexport type EcmaVersion = ... independently to beingexport type EcmaVersion = eslint.Linter.EcmaVersion; as that'd solve the issue in the future but I figured there must be a reason for manually definingEcmaVersion. Perhaps peer dependency issues?

dangrussell reacted with thumbs up emojinikolawork reacted with heart emoji
@typescript-eslint
Copy link
Contributor

Thanks for the PR,@DavidArchibald!

typescript-eslint is a 100% community driven project, and we are incredibly grateful that you are contributing to that community.

The core maintainers work on this in their personal time, so please understand that it may not be possible for them to review your work immediately.

Thanks again!


🙏Please, if you or your company is finding typescript-eslint valuable, help us sustain the project by sponsoring it transparently onhttps://opencollective.com/typescript-eslint.

@netlifyNetlify
Copy link

netlifybot commentedJun 13, 2025
edited
Loading

Deploy Preview fortypescript-eslint ready!

NameLink
🔨 Latest commitf6411ab
🔍 Latest deploy loghttps://app.netlify.com/projects/typescript-eslint/deploys/684c875fb0b02f0008e357ed
😎 Deploy Previewhttps://deploy-preview-11304--typescript-eslint.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.
Lighthouse
Lighthouse
1 paths audited
Performance: 64 (🔴 down 35 from production)
Accessibility: 100 (no change from production)
Best Practices: 100 (no change from production)
SEO: 98 (no change from production)
PWA: 80 (no change from production)
View the detailed breakdown and full score reports

To edit notification comments on pull requests, go to yourNetlify project configuration.

@nx-cloudNx Cloud
Copy link

nx-cloudbot commentedJun 13, 2025
edited
Loading

View yourCI Pipeline Execution ↗ for commitf6411ab.

CommandStatusDurationResult
nx test eslint-plugin --coverage=false✅ Succeeded5m 5sView ↗
nx run-many -t typecheck✅ Succeeded1m 58sView ↗
nx test typescript-estree --coverage=false✅ Succeeded19sView ↗
nx run-many -t lint✅ Succeeded13sView ↗
nx test eslint-plugin-internal --coverage=false✅ Succeeded7sView ↗
nx run generate-configs✅ Succeeded10sView ↗
nx run integration-tests:test✅ Succeeded<1sView ↗
nx run types:build✅ Succeeded1sView ↗
Additional runs (27)✅ Succeeded...View ↗

☁️Nx Cloud last updated this comment at2025-06-13 20:29:57 UTC

@DavidArchibaldDavidArchibald changed the titleAdd 2026/17 to EcmaVersionfix: add 2026/17 to EcmaVersionJun 13, 2025
@bradzacherbradzacher changed the titlefix: add 2026/17 to EcmaVersionfix(types): add 2026/17 to EcmaVersionJun 13, 2025
Copy link
Member

@bradzacherbradzacher left a comment

Choose a reason for hiding this comment

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

Thanks!

Sign up for freeto subscribe to this conversation on GitHub. Already have an account?Sign in.
Reviewers

@bradzacherbradzacherbradzacher approved these changes

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

2 participants
@DavidArchibald@bradzacher

[8]ページ先頭

©2009-2025 Movatter.jp