Skip to content

build(deps-dev): bump typescript from 6.0.3 to 7.0.2#2284

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/typescript-7.0.2
Open

build(deps-dev): bump typescript from 6.0.3 to 7.0.2#2284
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/typescript-7.0.2

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Jul 13, 2026

Copy link
Copy Markdown
Contributor

Bumps typescript from 6.0.3 to 7.0.2.

Commits
Maintainer changes

This version was pushed to npm by microsoft1es, a new releaser for typescript since your current version.


@dependabot dependabot Bot added dependencies Pull requests that update a dependency file javascript Pull requests that update Javascript code labels Jul 13, 2026
github-actions[bot]
github-actions Bot previously approved these changes Jul 13, 2026
@webstech

Copy link
Copy Markdown
Contributor

@dscho The typescript compiler has been rewritten in Go. PR #2286 adds ts v7 support for typia but doesn't force an additional package it needs (ttsc). The jest related stuff (ts-*) is broken and it is not clear what the plans are for some of the projects. Just starting researching so may have missed some things.

Aside: there appears to be a move to (re)write js tooling in high level languages. Performance seems to be a big deal.

@dscho

dscho commented Jul 14, 2026

Copy link
Copy Markdown
Member

@webstech thanks for taking care of this, sounds like a ton of work!

@webstech

Copy link
Copy Markdown
Contributor

@webstech thanks for taking care of this, sounds like a ton of work!

We will see if I can take care of this 😕. Using the typescript team's (MS) suggestion of installing two versions, linting works (ie typescript-eslint works).

jest is another matter. It was semi-abandoned for awhile so I have lost some confidence in it. Not sure node:test can replace it though. Do you have any opinions about vitest? I had one test working but there is some typia config to work out. If you are interested in exploring vitest, I will work on it some more.

As an aside, the compiler is faster.

@dscho

dscho commented Jul 15, 2026

Copy link
Copy Markdown
Member

Do you have any opinions about vitest?

@webstech yes, I do ;-) Somebody tried to sneak it into the setup-git-for-windows-sdk Action while upgrading to NodeJS 24. Naturally, I was quite opposed at first. But they had a good point: ESM are first-class citizens in vitest, while they are ridiculously uncared-for by Jest. So I gave in, and when I'm looking back to Jest it's actually without any nostalgia or longing. In many ways, vitest feels like "Jest Done Right", testament to which is the vastly lower update frequency.

tl;dr I like the idea of moving to vitest.

@webstech

Copy link
Copy Markdown
Contributor

I like the idea of moving to vitest.

You might like it even more now that the tests have been run with it. GGG has never built the tests but that seems to be needed now. It may be normal since I didn't find projects talking about having to do it.

Looking at the vitest config a bit more before submitting a PR. Maybe some parallelism that can be added to improve performance. The current elapsed time is about the same as jest.

Bumps [typescript](https://github.com/microsoft/TypeScript) from 6.0.3 to 7.0.2.
- [Release notes](https://github.com/microsoft/TypeScript/releases)
- [Commits](https://github.com/microsoft/TypeScript/commits)

---
updated-dependencies:
- dependency-name: typescript
  dependency-version: 7.0.2
  dependency-type: direct:development
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot
dependabot Bot force-pushed the dependabot/npm_and_yarn/typescript-7.0.2 branch from 4d0afec to a3fe47f Compare July 22, 2026 22:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file javascript Pull requests that update Javascript code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants