chore(deps)!: update dependency typescript to v5

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
typescript (source)	~4.9.5 -> ~5.3.3

---

Release Notes

Microsoft/TypeScript (typescript)

v5.3.3: TypeScript 5.3.3

Compare Source

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

• fixed issues query for Typescript 5.3.0 (Beta).
• fixed issues query for Typescript 5.3.1 (RC).
• fixed issues query for Typescript 5.3.2 (Stable).
• fixed issues query for Typescript 5.3.3 (Stable).

Downloads are available on:

• NuGet package

v5.3.2: TypeScript 5.3

Compare Source

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

• fixed issues query for Typescript 5.3.0 (Beta).
• fixed issues query for Typescript 5.3.1 (RC).
• fixed issues query for Typescript 5.3.2 (Stable).

Downloads are available on:

• NuGet package

v5.2.2: TypeScript 5.2

Compare Source

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

• fixed issues query for Typescript 5.2.0 (Beta).
• fixed issues query for Typescript 5.2.1 (RC).
• fixed issues query for Typescript 5.2.2 (Stable).

Downloads are available on:

• NuGet package

v5.1.6: TypeScript 5.1.6

Compare Source

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

• fixed issues query for Typescript v5.1.0 (Beta).
• fixed issues query for Typescript v5.1.1 (RC).
• fixed issues query for Typescript v5.1.2 (Stable).
• fixed issues query for Typescript v5.1.3 (Stable).
• (5.1.4 intentionally skipped)
• fixed issues query for Typescript v5.1.5 (Stable).
• fixed issues query for Typescript v5.1.6 (Stable).

Downloads are available on npm

v5.1.5: TypeScript 5.1.5

Compare Source

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

• fixed issues query for Typescript v5.1.0 (Beta).
• fixed issues query for Typescript v5.1.1 (RC).
• fixed issues query for Typescript v5.1.2 (Stable).
• fixed issues query for Typescript v5.1.3 (Stable).
• (5.1.4 intentionally skipped)
• fixed issues query for Typescript v5.1.5 (Stable).

Downloads are available on:

• npm
• NuGet package

v5.1.3: TypeScript 5.1.3

Compare Source

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

• fixed issues query for Typescript 5.1.0 (Beta).
• fixed issues query for Typescript 5.1.1 (RC).
• fixed issues query for Typescript 5.1.3 (Stable).

Downloads are available on:

• NuGet package

v5.0.4: TypeScript 5.0.4

Compare Source

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

• fixed issues query for Typescript v5.0.0 (Beta).
• fixed issues query for Typescript v5.0.1 (RC).
• fixed issues query for Typescript v5.0.2 (Stable).
• fixed issues query for Typescript v5.0.3 (Stable).
• fixed issues query for Typescript v5.0.4 (Stable).

Downloads are available on:

• npm
• NuGet package

v5.0.3: TypeScript 5.0.3

Compare Source

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

• fixed issues query for Typescript v5.0.0 (Beta).
• fixed issues query for Typescript v5.0.1 (RC).
• fixed issues query for Typescript v5.0.2 (Stable).
• fixed issues query for Typescript v5.0.3 (Stable).

Downloads are available on:

• npm
• NuGet package

v5.0.2: TypeScript 5.0

Compare Source

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

• fixed issues query for Typescript v5.0.0 (Beta).
• fixed issues query for Typescript v5.0.1 (RC).
• fixed issues query for Typescript v5.0.2 (Stable).

Downloads are available on:

• npm
• NuGet package

---

Configuration

📅 Schedule: Branch creation - "before 4am on Monday" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate. View repository job log here.

[Shinigami92]

I assume this is currently just blocked by

• chore(deps): update doc-dependencies #1948

because it currently cannot extract something for the docs

[ST-DDT]

This might be blocked by #1952 as well and might need some manual updating as well.

[Shinigami92]

This might be blocked by #1952 as well and might need some manual updating as well.

Are you sure?
Please have a look into the CI
To me these looks like they are not affected by the linting step at all 🤔

[ST-DDT]

Please have a look into the CI

I did. The lint step is failing. Prettier requests some formatting to be applied to imports.
So either we have to update prettier or eslint or our source code. I dont know whether its an intentional change or one caused by an incompatibility. Why would updating typescript have an impact on the required import order?

We also have to update the test snapshots.

[Shinigami92]

Please have a look into the CI

I did. The lint step is failing. Prettier requests some formatting to be applied to imports. So either we have to update prettier or eslint or our source code. I dont know whether its an intentional change or one caused by an incompatibility. Why would updating typescript have an impact on the required import order?

We also have to update the test snapshots.

Ah I see, I checked just the test CIs not the linting step.

But yes, somehow via the TS v5 <-> prettier changed 👀
I can not only observe this behavior in Faker, but also now in prettier/plugin-pug@54ffb01

[ST-DDT]

Well from the diff it looks like it just sorts the imports alphabetically, so it might not be actually blocking, but something that might change again with future updates.

Since it doesnt hurt, should we do the required steps to merge this PR? Are you interested or should I do it?

[Shinigami92]

Are you interested or should I do it?

I will try it :)

[Shinigami92]

Okay, lets wait a bit so the eslint + prettier ecosystem can stabilize itself
I highly assume that TS v5 did define a new kind of sort order, this will be fetch from the TS language server from https://github.com/simonhaenisch/prettier-plugin-organize-imports and then processed via prettier. And this will then checked against eslint prettier/prettier rule (https://github.com/prettier/eslint-plugin-prettier).

All these components need to be working with each other, and instead of hard trying from our side to push this, we can maybe just wait a week or two and come back until all these developers and contributors had a bit of time to keep up :)

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (aa183ad) 99.56% compared to head (d60bc95) 99.57%.

Additional details and impacted files

@@           Coverage Diff            @@
##             next    #1953    +/-   ##
========================================
  Coverage   99.56%   99.57%            
========================================
  Files        2807     2807            
  Lines      250525   250526     +1     
  Branches     1149      742   -407     
========================================
+ Hits       249447   249466    +19     
- Misses       1050     1060    +10     
+ Partials       28        0    -28     

Files	Coverage Δ
src/index.ts	100.00% <100.00%> (ø)

... and 29 files with indirect coverage changes

[ST-DDT]

It's okay from my side, but @ST-DDT should mark in his notes to reevaluate the ? generation when he switches to ts-ast / ts-morph and we get rid of typedoc

FFR: Refering to LiteralUnion<'a' | 'b'> -> 'a' | 'b' | ?

[Shinigami92]

We need to add a docs/guide/upgrading_v9/1953.md in this PR

[renovate]

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠ Warning: custom changes will be lost.