chore: update typescript to 5.3

[ForsakenHarmony]

Why?

Need it for import attribute support (import x from 'y' with { ... })

Closes PACK-2131

[ijjk]

Stats from current PR

Default Build (Increase detected ⚠️)

General Overall increase ⚠️

	vercel/next.js canary	vercel/next.js hrmny/update-typescript	Change
buildDuration	13.8s	13.9s	N/A
buildDurationCached	7.5s	6.5s	N/A
nodeModulesSize	197 MB	197 MB	⚠️ +12.5 kB
nextStartRea..uration (ms)	411ms	413ms	N/A

Client Bundles (main, webpack)

	vercel/next.js canary	vercel/next.js hrmny/update-typescript	Change
2453-HASH.js gzip	30.2 kB	30.2 kB	N/A
3304.HASH.js gzip	181 B	181 B	✓
3f784ff6-HASH.js gzip	53.7 kB	53.7 kB	N/A
8299-HASH.js gzip	5.04 kB	5.04 kB	N/A
framework-HASH.js gzip	45.2 kB	45.2 kB	✓
main-app-HASH.js gzip	242 B	242 B	✓
main-HASH.js gzip	32.2 kB	32.2 kB	N/A
webpack-HASH.js gzip	1.68 kB	1.68 kB	N/A
Overall change	45.6 kB	45.6 kB	✓

Legacy Client Bundles (polyfills)

	vercel/next.js canary	vercel/next.js hrmny/update-typescript	Change
polyfills-HASH.js gzip	31 kB	31 kB	✓
Overall change	31 kB	31 kB	✓

Client Pages

	vercel/next.js canary	vercel/next.js hrmny/update-typescript	Change
_app-HASH.js gzip	196 B	197 B	N/A
_error-HASH.js gzip	184 B	184 B	✓
amp-HASH.js gzip	505 B	505 B	✓
css-HASH.js gzip	324 B	325 B	N/A
dynamic-HASH.js gzip	2.5 kB	2.5 kB	N/A
edge-ssr-HASH.js gzip	258 B	258 B	✓
head-HASH.js gzip	352 B	352 B	✓
hooks-HASH.js gzip	370 B	371 B	N/A
image-HASH.js gzip	4.2 kB	4.2 kB	✓
index-HASH.js gzip	259 B	259 B	✓
link-HASH.js gzip	2.67 kB	2.67 kB	N/A
routerDirect..HASH.js gzip	314 B	312 B	N/A
script-HASH.js gzip	386 B	386 B	✓
withRouter-HASH.js gzip	309 B	309 B	✓
1afbb74e6ecf..834.css gzip	106 B	106 B	✓
Overall change	6.56 kB	6.56 kB	✓

Client Build Manifests

	vercel/next.js canary	vercel/next.js hrmny/update-typescript	Change
_buildManifest.js gzip	483 B	485 B	N/A
Overall change	0 B	0 B	✓

Rendered Page Sizes

	vercel/next.js canary	vercel/next.js hrmny/update-typescript	Change
index.html gzip	530 B	529 B	N/A
link.html gzip	542 B	542 B	✓
withRouter.html gzip	525 B	523 B	N/A
Overall change	542 B	542 B	✓

Edge SSR bundle Size

	vercel/next.js canary	vercel/next.js hrmny/update-typescript	Change
edge-ssr.js gzip	95 kB	95 kB	N/A
page.js gzip	3.07 kB	3.07 kB	N/A
Overall change	0 B	0 B	✓

Middleware size

	vercel/next.js canary	vercel/next.js hrmny/update-typescript	Change
middleware-b..fest.js gzip	622 B	624 B	N/A
middleware-r..fest.js gzip	151 B	151 B	✓
middleware.js gzip	25.5 kB	25.5 kB	N/A
edge-runtime..pack.js gzip	839 B	839 B	✓
Overall change	990 B	990 B	✓

Next Runtimes

	vercel/next.js canary	vercel/next.js hrmny/update-typescript	Change
app-page-exp...dev.js gzip	171 kB	171 kB	✓
app-page-exp..prod.js gzip	96.7 kB	96.7 kB	✓
app-page-tur..prod.js gzip	98.5 kB	98.5 kB	✓
app-page-tur..prod.js gzip	92.9 kB	92.9 kB	✓
app-page.run...dev.js gzip	150 kB	150 kB	✓
app-page.run..prod.js gzip	91.4 kB	91.4 kB	✓
app-route-ex...dev.js gzip	21.3 kB	21.3 kB	✓
app-route-ex..prod.js gzip	15 kB	15 kB	✓
app-route-tu..prod.js gzip	15 kB	15 kB	✓
app-route-tu..prod.js gzip	14.8 kB	14.8 kB	✓
app-route.ru...dev.js gzip	20.9 kB	20.9 kB	✓
app-route.ru..prod.js gzip	14.8 kB	14.8 kB	✓
pages-api-tu..prod.js gzip	9.51 kB	9.51 kB	✓
pages-api.ru...dev.js gzip	9.79 kB	9.79 kB	✓
pages-api.ru..prod.js gzip	9.51 kB	9.51 kB	✓
pages-turbo...prod.js gzip	22.3 kB	22.3 kB	✓
pages.runtim...dev.js gzip	23 kB	23 kB	✓
pages.runtim..prod.js gzip	22.3 kB	22.3 kB	✓
server.runti..prod.js gzip	50.6 kB	50.6 kB	✓
Overall change	950 kB	950 kB	✓

build cache Overall increase ⚠️

	vercel/next.js canary	vercel/next.js hrmny/update-typescript	Change
0.pack gzip	1.56 MB	1.56 MB	N/A
index.pack gzip	104 kB	105 kB	⚠️ +963 B
Overall change	104 kB	105 kB	⚠️ +963 B

Diff details

Diff for middleware.js

Diff too large to display

Commit: e4094c5

[styfle]

Thanks!

[ForsakenHarmony]

• chore: update typescript to 5.3 #59494 👈
• canary

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @ForsakenHarmony and the rest of your teammates on Graphite

[ijjk]

Tests Passed

[ForsakenHarmony]

Currently broken because typescript 5.3 adds all .d.ts files used in an output file into it as a /// <reference with no way to turn it off

sucks, but it is the right thing to do, we probably need to get rid of the split between types/misc.d.ts and types/compiled.d.ts
should probably copy all @types packages into next/dist/compiled as well

[socket-security]

New and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Package	New capabilities	Transitives	Size	Publisher
npm/@next/bundle-analyzer@14.1.1-canary.82	Transitive: environment, filesystem, network, shell	+18	2.19 MB	vercel-release-bot
npm/@next/eslint-plugin-next@14.1.1-canary.82	filesystem Transitive: environment, shell	+33	2.99 MB	vercel-release-bot
npm/@next/font@14.1.1-canary.82	Transitive: environment, filesystem, network, shell, unsafe	+89	113 MB	vercel-release-bot
npm/eslint-config-next@14.1.1-canary.82	unsafe Transitive: environment, eval, filesystem, shell	+285	99.4 MB	vercel-release-bot
npm/next@14.1.1-canary.82	environment, filesystem, network, shell, unsafe	+88	111 MB	vercel-release-bot
npm/typescript@5.3.3	None	0	32 MB	typescript-bot

🚮 Removed packages: npm/typescript@5.2.2

View full report↗︎

[sokra]

Ship it?

[socket-security]

🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎

To accept the risk, merge this PR and you will not be notified again.

Alert	Package	Note	Source
Telemetry	npm/next@14.1.1-canary.82	Note: Can be disabled by setting the environment variable NEXT_TELEMETRY_DISABLED=1 . See https://nextjs.org/telemetry for more information	package.json packages/font/package.json packages/third-parties/package.json pnpm-lock.yaml

View full report↗︎

Next steps

What is telemetry?

This package contains telemetry which tracks how it is used.

Most telemetry comes with settings to disable it. Consider disabling telemetry if you do not want to be tracked.

Take a deeper look at the dependency

Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev.

Remove the package

If you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency.

Mark a package as acceptable risk

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of ecosystem/package-name@version specifiers. e.g. @SocketSecurity ignore npm/foo@1.0.0 or ignore all packages with @SocketSecurity ignore-all

• @SocketSecurity ignore npm/next@14.1.1-canary.82