mirror of
https://github.com/apache/airflow.git
synced 2026-11-04 07:12:48 +00:00
Jason(Zhe-You) Liu
11ef1fb282
* Verify TypeScript SDK package contents * Add --all-files to verify-ts-sdk-package doc command * Smoke-test the Dag-authoring entrypoints the package publishes The consumer smoke test asserted a registerTask export that the SDK no longer has, so it would have failed every release regardless of whether the tarball was sound. It now checks the Dag, DagRegistry, and serveDags entrypoints the documented authoring API is built from, and reports which one is missing instead of exiting without a message. * Import every exports subpath in the package smoke test The check only imported the package root, so the ./coordinator subpath was confirmed present in the tarball and never actually resolved. A subpath can ship and still fail to import when its exports conditions are wrong or an internal import is broken, which is the failure a consumer would hit first. Deriving the list from the exports keys also means a new subpath is covered without touching this script. * Unit-test the TypeScript SDK package verification helpers The verification ran as top-level statements, so importing the module packed the SDK and installed it from the registry, and none of the logic that decides what may ship could be exercised without a full release rehearsal. Splitting the allowlist, entry-point derivation, pack-metadata parsing, and smoke-test construction into importable functions behind an entrypoint guard puts that logic under test, matching the shape of the release input validator.
13 lines
263 B
JSON
13 lines
263 B
JSON
{
|
|
"extends": "./tsconfig.json",
|
|
"compilerOptions": {
|
|
"noEmit": false,
|
|
"outDir": "./dist",
|
|
"rootDir": "./src",
|
|
"sourceMap": false,
|
|
"declarationMap": false
|
|
},
|
|
"include": ["src/**/*.ts"],
|
|
"exclude": ["src/**/*.test.ts", "tests/**/*"]
|
|
}
|