-
Notifications
You must be signed in to change notification settings - Fork 0
build: fix release pipeline so first publish can ship #5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,5 +1,6 @@ | ||
| { | ||
| "extends": "./tsconfig.json", | ||
| "exclude": ["node_modules", "dist", "**/testData", "**/*.test.ts"], | ||
|
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. [P2] Because
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. [P2] This |
||
| "compilerOptions": { | ||
| "module": "commonjs", | ||
| "outDir": "dist/cjs", | ||
|
|
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[P2] This changes the package contents to fix a release failure, but there’s still no regression test for the tarball contents.
prepublishOnlybuilds and runs ATTW, yet nothing asserts thatnpm packomits compiled*.test.*files, so a futuretsconfig/filesdrift can silently reintroduce the same breakage. Add a small packaging smoke test in CI that inspectsnpm pack --jsonoutput or the packed file list.