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

feat: support TypeScript 5.1#7088

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

@JoshuaKGoldberg
Copy link
Member

@JoshuaKGoldbergJoshuaKGoldberg commentedJun 6, 2023
edited
Loading

Note: This doesn't Block You From Linting TypeScript 5.1

You can still usetypescript@>=5.1 with@typescript-eslint/eslint-plugin &@typescript-eslint/parser. There are no breaking changes in TS 5.1 that would block you from linting existing code. JSX namespaces (<MyComponent a:b />) should generally be linted properly.

Until this PR is merged and a new set of typescript-eslint package versions are released, your console may see a log likeWARNING: You are currently running a version of TypeScript which is not officially supported by @typescript-eslint/typescript-estree..

Status Update: June 26th 2023

Looks like TypeScript's latest releases have fixed the issue. We should be ready to release a new version with this PR's changes soon - pending review.

Status Update: June 9 2023

This PR is blocked on out-of-memory (OOM) errors running a set of important unit tests for the parser. The OOM error only occurs with TypeScript 5.1, not locally.

We're working on identifying which commit to TypeScript introduced the change that coincides with this OOM error being introduced. In#7091 we narrowed it down as follows:

  • ✅ Running withtypescript@5.1.0-dev.20230301does not exhibit the OOM error
  • ❌ Running withtypescript@5.1.0-dev.20230302does exhibit the OOM error

Our next step will be to write a script to run against individual TypeScript commits.

It looks likemicrosoft/TypeScript#54542 is the root of the OOM. At least, from running on recent TypeScript commits, that's the first one that has the OOM occur. TBD once it's fixed.

Thanks to@jakebailey from the TypeScript team for helping us with this! ❤️


PR Checklist

Overview

Bumps the supported ranges perhttps://typescript-eslint.io/maintenance/versioning/dependant-version-upgrades#adding-support-for-a-new-typescript-version. Since we didn't have an RC PR, this merges the PR steps a bit.

xiaoxian521, rkuykendall, azat-io, andriyor, joealden, dotoleeoak, and yvele reacted with thumbs up emojiyvele reacted with hooray emojiaried3r, xiaoxian521, billyzkid, Eusebiotrigo, andriyor, and yvele reacted with rocket emoji
@typescript-eslint
Copy link
Contributor

Thanks for the PR,@JoshuaKGoldberg!

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.

@netlify
Copy link

netlifybot commentedJun 6, 2023
edited
Loading

Deploy Preview fortypescript-eslint failed.

NameLink
🔨 Latest commit3a01637
🔍 Latest deploy loghttps://app.netlify.com/sites/typescript-eslint/deploys/649f1795a0c6860007244359

@nx-cloud
Copy link

nx-cloudbot commentedJun 7, 2023
edited
Loading

☁️ Nx Cloud Report

CI is running/has finished running commands for commit3a01637. As they complete they will appear below. Click to see the status, the terminal output, and the build insights.

📂 See all runs for this branch


✅ Successfully ran 25 targets

Sent with 💌 fromNxCloud.

@JoshuaKGoldbergJoshuaKGoldberg marked this pull request as ready for reviewJune 7, 2023 02:15
@JoshuaKGoldberg
Copy link
MemberAuthor

Run ./.github/actions/wait-for-netlify/home/runner/work/typescript-eslint/typescript-eslint/node_modules/@actions/core/lib/core.js:106        throw new Error(`Input required and not supplied: ${name}`);        ^Error: Input required and not supplied: netlify_token

@JamesHenry something funky with the new action, perhaps?https://github.com/typescript-eslint/typescript-eslint/actions/runs/5195237524/jobs/9367800550?pr=7088

@JoshuaKGoldberg
Copy link
MemberAuthor

PASS  tests/lib/node-utils.test.ts PASS  tests/lib/parse.project-true.test.ts<--- Last few GCs --->[2972:0x61b15c0]   201164 ms: Mark-sweep (reduce) 2037.5 (2051.0) -> 2036.7 (2052.5) MB, 2662.2 / 0.0 ms  (average mu = 0.171, current mu = 0.014) allocation failure scavenge might not succeed[2972:0x61b15c0]   203868 ms: Mark-sweep (reduce) 2037.8 (2051.5) -> 2037.3 (2052.8) MB, [26](https://github.com/typescript-eslint/typescript-eslint/actions/runs/5195237524/jobs/9367799309?pr=7088#step:6:27)32.6 / 0.0 ms  (average mu = 0.102, current mu = 0.026) allocation failure scavenge might not succeed<--- JS stacktrace --->FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory 1: 0xa3ad50 node::Abort() [/opt/hostedtoolcache/node/14.21.3/x64/bin/node]

sigh.

bradzacher
bradzacher previously approved these changesJun 7, 2023
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.

One case that would be worth adding a test for:
<foo-bar:baz-bam />

Both the ns and name of the namespace are allowed to be valid JSX identifiers!

Otherwise this is all LGTM
Once you land it we can do an out-of-band release to get it out and keep the early adopters happy!

JoshuaKGoldberg reacted with rocket emoji

// Both of these are equivalent:
constx=<Fooa:b="hello"/>;
consty=<Fooa :b="hello"/>;
Copy link
Member

Choose a reason for hiding this comment

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

cool - this case actually used to be an error pre 5.1!

JoshuaKGoldberg reacted with rocket emoji
@JamesHenry
Copy link
Member

JamesHenry commentedJun 7, 2023
edited
Loading

Run ./.github/actions/wait-for-netlify/home/runner/work/typescript-eslint/typescript-eslint/node_modules/@actions/core/lib/core.js:106        throw new Error(`Input required and not supplied: ${name}`);        ^Error: Input required and not supplied: netlify_token

@JamesHenry something funky with the new action, perhaps?https://github.com/typescript-eslint/typescript-eslint/actions/runs/5195237524/jobs/9367800550?pr=7088

Oh sorry, I reckon it could be that the secret doesn’t work as an input when you’re coming from a fork…

I will figure out how this has been workable for other actions in the past

JoshuaKGoldberg reacted with heart emoji

@JamesHenry
Copy link
Member

@JoshuaKGoldberg@bradzacher I can't find any evidence that this ever worked. I think the secret won't be populated on forks which makes sense.

I have therefore just pushed a commit to the branch which should should hopefully amend things to only run the Website Tests when not on a fork

@JamesHenry
Copy link
Member

I thought that should work based on this answer:https://github.com/orgs/community/discussions/26409#discussioncomment-3251822

anyone know the right syntax here?

@bradzacher
Copy link
Member

That's all we've got here:

if:github.repository == 'typescript-eslint/typescript-eslint' && github.ref == 'refs/heads/main'

IDK why it wouldn't be working there?

@bradzacher
Copy link
Member

@JoshuaKGoldberg once you've got all the tests passing locally feel free to just land this to main.

We can follow up with a fix commit if any CIs fail on main.

JoshuaKGoldberg reacted with thumbs up emoji

@JoshuaKGoldberg
Copy link
MemberAuthor

JoshuaKGoldberg commentedJun 9, 2023
edited
Loading

Ah, this may be from adifferent TypeScript issue likely to be fixed soon:microsoft/TypeScript#54542

@JoshuaKGoldbergJoshuaKGoldberg removed the blocked by another issueIssues which are not ready because another issue needs to be resolved first labelJun 26, 2023
@codecov
Copy link

codecovbot commentedJun 26, 2023
edited
Loading

Codecov Report

Merging#7088 (3a01637) intomain (f74862c) willdecrease coverage by0.04%.
The diff coverage is33.33%.

Additional details and impacted files
@@            Coverage Diff             @@##             main    #7088      +/-   ##==========================================- Coverage   87.43%   87.39%   -0.04%==========================================  Files         386      386                Lines       13192    13198       +6       Branches     3872     3873       +1     ==========================================+ Hits        11534    11535       +1- Misses       1292     1296       +4- Partials      366      367       +1
FlagCoverage Δ
unittest87.39% <33.33%> (-0.04%)⬇️

Flags with carried forward coverage won't be shown.Click here to find out more.

Impacted FilesCoverage Δ
packages/typescript-estree/src/convert.ts29.22% <0.00%> (-0.15%)⬇️
...ipt-estree/src/parseSettings/warnAboutTSVersion.ts93.33% <100.00%> (ø)

... and2 files with indirect coverage changes

package.json Outdated
"tslint":"^6.1.3",
"tsx":"^3.12.1",
"typescript":">=3.3.1 <5.1.0"
"typescript":"npm:@typescript-deploys/pr-build@5.2.0-pr-54781-9"
Copy link
Member

Choose a reason for hiding this comment

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

@JoshuaKGoldberg is the regression going to be patch fixed in 5.1? Or is it going to wait for 5.2?

Copy link
MemberAuthor

Choose a reason for hiding this comment

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

@jakebailey indicated it should be patched soon

bradzacher reacted with thumbs up emoji
Copy link
Collaborator

Choose a reason for hiding this comment

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

Yeah there will be a patch release of 5.1 in the next day or so.

bradzacher, jaylinski, wesleydebruijn, Jolg42, scottbedard, and azat-io reacted with hooray emoji

Choose a reason for hiding this comment

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

5.1.6 isout on npm since yesterday, although not visible inhttps://github.com/microsoft/TypeScript/releases yet.

@JoshuaKGoldbergJoshuaKGoldberg merged commit4bf2d73 intotypescript-eslint:mainJun 30, 2023
@JoshuaKGoldbergJoshuaKGoldberg deleted the typescript-5.1 branchJune 30, 2023 23:21
//@ts-check

constts=require('typescript');
console.log('Running with TypeScript version:',ts.version);
Copy link
MemberAuthor

Choose a reason for hiding this comment

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

oops, meant to remove this... will do later 😄

aimichelle pushed a commit to pixie-io/pixie that referenced this pull requestJul 13, 2023
Summary: To get the fixes from [this saga ofbugs](typescript-eslint/typescript-eslint#7088).Relevant Issues: N/AType of change: /kind bugfixTest Plan: `yarn typecheck && yarn lint`. Editors should still behave.Signed-off-by: Nick Lanam <nlanam@pixielabs.ai>
@github-actionsgithub-actionsbot locked asresolvedand limited conversation to collaboratorsJul 14, 2023
Sign up for freeto subscribe to this conversation on GitHub. Already have an account?Sign in.

Reviewers

@bradzacherbradzacherbradzacher left review comments

+2 more reviewers

@jakebaileyjakebaileyjakebailey left review comments

@wojtekmajwojtekmajwojtekmaj left review comments

Reviewers whose approvals may not affect merge requirements

Assignees

No one assigned

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

TypeScript 5.1 Support

5 participants

@JoshuaKGoldberg@JamesHenry@bradzacher@jakebailey@wojtekmaj

[8]ページ先頭

©2009-2025 Movatter.jp