Make it possible for packages to build#1717
Merged
rowanmanning merged 1 commit into2026-majorsfrom Mar 16, 2026
Merged
Conversation
This means packages can have their own build steps, allowing us to migrate them to TypeScript one-by-one instead of as one massive PR. See-also: https://financialtimes.atlassian.net/browse/CPREL-1481
rowanmanning
requested review from
a team,
ft-dependency-auto-merger and
next-team
as code owners
rowanmanning
force-pushed
the
package-build-steps
branch
from
85dca25 to
ffb4d37
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This means packages can have their own build steps, allowing us to migrate them to TypeScript one-by-one instead of as one massive PR.
See-also: CPREL-1481
Note
this is being PRed into the
2026-majorsbranch, a long-running branch for our milestone.