feat(ast): normalize swc_ecma_ast serde output for ts-estree

[kdy1]

Summary

• normalize swc_ecma_ast serde-impl output at the Program entrypoint to a TypeScript-ESTree / typescript-eslint-oriented shape
• remove internal serialization details like span and ctxt, and normalize representative node shapes including Program, ChainExpression, MemberExpression for super, PrivateIdentifier, PropertyDefinition, MethodDefinition, and TS* node names
• add parser-driven serialization tests covering program roots, class/private fields, constructor parameter properties, optional chaining, and key TypeScript declaration/signature nodes

Details

• keep deserialization on the existing SWC-facing format while making serialization intentionally asymmetric
• add a normalization layer in swc_ecma_ast::serde_impl and wire Program to use it for serialization
• make SyntaxContext-backed ctxt fields deserialize with defaults so older JSON inputs without ctxt continue to parse

Testing

• git submodule update --init --recursive
• cargo fmt --all
• cargo test -p swc_ecma_ast
• cargo test -p swc_ecma_ast --features serde-impl
• cargo clippy --all --all-targets -- -D warnings
• cargo clippy -p swc_ecma_ast --features serde-impl --all-targets -- -D warnings

[changeset-bot]

⚠️ No Changeset found

Latest commit: 44232e9

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	glob@​8.1.0
	jest@​29.7.0
	lodash@​4.17.21
	npm-run-all@​4.1.5
	progress@​2.0.3
	sourcemap-validator@​2.1.0
	react@​17.0.2
	husky@​7.0.4
	regenerator-runtime@​0.13.11
	reflect-metadata@​0.1.14
	@​types/​node@​20.12.12
	swc-plugin-coverage-instrument@​0.0.26
	js-beautify@​1.14.7
	ts-node@​10.9.1
	prop-types@​15.8.1
	source-map-support@​0.5.21
	tsx@​3.14.0
	semver@​7.5.4
	octokit@​3.2.1
	zx@​8.1.4
	webpack-dev-server@​3.11.3
	source-map@​0.7.4
	terser@​5.17.6
	yaml@​2.4.5
	typescript@​5.5.4
	typescript@​5.3.3
	prettier@​2.8.8
	webpack-cli@​3.3.12
	mocha@​9.2.2
	webpack@​4.47.0
	lint-staged@​12.5.0

View full report

[socket-security]

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action	Severity	Alert  (click "▶" to expand/collapse)
Warn		Obfuscated code: npm js-beautify is 100.0% likely obfuscated Confidence: 1.00 Location: Package overview From: package.json → npm/js-beautify@1.14.7 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: 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@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/js-beautify@1.14.7. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report

[github-actions]

Binary Sizes

File	Size
swc.linux-x64-gnu.node	28M (29142984 bytes)

Commit: dedaba9

[codspeed-hq]

Merging this PR will not alter performance

✅ 219 untouched benchmarks

---

_{Comparing kdy1:kdy1/ts-estree-serde-output (44232e9) with main (236eff0)¹}

Footnotes

1. No successful run was found on main (87dee57) during the generation of this report, so 236eff0 was used instead as the comparison base. There might be some changes unrelated to this pull request in this report. ↩