Prepare next update of TypeScript

[samchon]

This pull request includes updates to the typescript version across various package.json files and changes to the npm install command in the GitHub Actions workflow.

Updates to typescript version:

• benchmark/package.json: Updated typescript version to 5.9.0-dev.20250223.
• package.json: Updated typescript version to 5.9.0-dev.20250223 in devDependencies and modified the range in peerDependencies to >=4.8.0 <5.10.0. [1] [2]
• test-error/package.json: Updated typescript version to 5.9.0-dev.20250223.
• test-esm/package.json: Updated typescript version to 5.9.0-dev.20250223.
• test/package.json: Updated typescript version to 5.9.0-dev.20250223.

Changes to GitHub Actions workflow:

• .github/workflows/build.yml: Modified npm install command to use the --force flag in multiple job steps. [1] [2] [3] [4]

[socket-security]

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

Package	New capabilities	Transitives	Size	Publisher
npm/[email protected]	filesystem, shell Transitive: environment	+19	1.72 MB	tschaub
npm/[email protected]	None	0	176 kB	pieroxy
npm/[email protected]	None	0	22.9 MB	typescript-bot

🚮 Removed packages: npm/@types/[email protected], npm/@types/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected]

View full report↗︎

[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	CI
Possible typosquat attack	npm/[email protected]	Did you mean: emoji-regex~~-xs~~	⚠︎

View full report↗︎

Next steps

What is a typosquat?

Package name is similar to other popular packages and may not be the package you want.

Use care when consuming similarly named packages and ensure that you did not intend to consume a different package. Malicious packages often publish using similar names as existing popular packages.

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/[email protected] or ignore all packages with @SocketSecurity ignore-all

• @SocketSecurity ignore npm/[email protected]

[pkg-pr-new]

Open in Stackblitz

npm i https://pkg.pr.new/typia@1509

commit: 738a908

[samchon]

No bug detected