Skip to content

chore: update typescript to 5.8.3#8

Open
frontend-updates[bot] wants to merge 1 commit into
mainfrom
chore/update-typescript-to-5.8.3
Open

chore: update typescript to 5.8.3#8
frontend-updates[bot] wants to merge 1 commit into
mainfrom
chore/update-typescript-to-5.8.3

Conversation

@frontend-updates

@frontend-updates frontend-updates Bot commented Apr 24, 2025

Copy link
Copy Markdown

This PR was created by Simple Frontend (Jeremy) following an important release for typescript.

TypeScript 5.8.3

The most impactful changes are coming from 5.8 update with the new --erasableSyntaxOnly option.

As Node.js 23.6 unflagged experimental support for running TypeScript files directly, we can now run TypeScript navitely using Node.js. However this obviously would not work if you have TypeScript-specific syntax with runtime semantics like enums. When the --erasableSyntaxOnly is enabled, Typescript will now prevent you to use constructs that cannot be erased.

Another important thing to note is import assertions restriction under --module nodenext. TypeScript 5.8 now aligns with Node.j 22 and no longer accepts import assertions using the assert syntax and you have to use the with keyword.

// An import assertion ❌ - not future-compatible with most runtimes.
import data from "./data.json" assert { type: "json" };

// An import attribute ✅ - the preferred way to import a JSON file.
import data from "./data.json" with { type: "json" };

Read the full release notes here and happy update!

@vercel

vercel Bot commented Apr 24, 2025

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
automated-end-to-end-tests-example ✅ Ready (Inspect) Visit Preview 💬 Add feedback Apr 24, 2025 0:31am

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant