build(client-utils): Fix type generation for ESM and add exports field #18822
Conversation
This file contains 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
github-actions
bot
added
area: build
⯆ @fluid-example/bundle-size-tests: -85.55 KB
Baseline commit: 04a597c |
tylerbutler
commented
Dec 14, 2023
tylerbutler
commented
Dec 14, 2023
github-actions
bot
removed
area: runtime
tylerbutler
changed the title
Josmithr
approved these changes
Dec 14, 2023
tyler-cai-microsoft
pushed a commit
to tyler-cai-microsoft/FluidFramework
that referenced
this pull request
Jan 10, 2024
microsoft#18822) This PR updates client-utils to: - generate proper types in ESM builds - enable type testing - builds tests using node16 module resolution It does NOT add an exports field, because doing that right now breaks a lot of downstream compilation. We should be able to resolve that once more/all packages are using node16 module resolution.
tyler-cai-microsoft
pushed a commit
to tyler-cai-microsoft/FluidFramework
that referenced
this pull request
Jan 10, 2024
microsoft#18822) This PR updates client-utils to: - generate proper types in ESM builds - enable type testing - builds tests using node16 module resolution It does NOT add an exports field, because doing that right now breaks a lot of downstream compilation. We should be able to resolve that once more/all packages are using node16 module resolution.
tyler-cai-microsoft
added a commit
that referenced
this pull request
Jan 10, 2024
Ported PRs: - #18822 - #18825 ## Description Our partner team notified us of a 150kb increase in size when consuming `2.0.0-internal.8.0.0`. After an investigation into our bundle size telemetry, it was determined that these two commits in main had reduced the bundle size by about ~100kb. ## Impact Reduce bundle size by ~100kb. --------- Co-authored-by: Tyler Butler <tylerbu@microsoft.com>
tyler-cai-microsoft
added a commit
that referenced
this pull request
Jan 10, 2024
Ported PRs: - #18822 - #18825 ## Description Our partner team notified us of a 150kb increase in size when consuming `2.0.0-internal.7.4.x`. After an investigation into our bundle size telemetry, it was determined that these two commits in main had reduced the bundle size by about ~100kb. ## Impact Reduce bundle size by ~100kb. --------- Co-authored-by: Tyler Butler <tylerbu@microsoft.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 PR updates client-utils to:
It does NOT add an exports field, because doing that right now breaks a lot of downstream compilation. We should be able to resolve that once more/all packages are using node16 module resolution.