Skip to content

chore(core): ensure package build order#7623

Merged
kuhe merged 1 commit intomainfrom
kuhe/build
Jan 6, 2026
Merged

chore(core): ensure package build order#7623
kuhe merged 1 commit intomainfrom
kuhe/build

Conversation

@kuhe
Copy link
Copy Markdown
Contributor

@kuhe kuhe commented Jan 6, 2026

Issue

n/a

Additional context

Some time ago the build order was changed from parallel types/es/cjs to types/es then cjs. This is to allow the cjs bundle to be built off the es artifact instead of the typescript source.

The two submodule-containing packages didn't receive this change, though they happened to work because of the timings involved (building submodules takes longer for CJS so ES finished by that time anyway).

This change ensures that the build order is correct and doesn't rely on a timing coincidence.

Checklist

  • If the PR is a feature, add integration tests (*.integ.spec.ts).
  • If you wrote E2E tests, are they resilient to concurrent I/O?
  • If adding new public functions, did you add the @public tag and enable doc generation on the package?

@kuhe kuhe requested a review from a team as a code owner January 6, 2026 16:04
@kuhe kuhe merged commit 3fa6ead into main Jan 6, 2026
7 checks passed
@kuhe kuhe deleted the kuhe/build branch January 6, 2026 18:27
@github-actions
Copy link
Copy Markdown

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs and link to relevant comments in this thread.

@github-actions github-actions Bot locked as resolved and limited conversation to collaborators Jan 21, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants