Skip to content
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

[Port v2int/7.4] Reduce v2int7.4 bundle size #19187

Conversation

tyler-cai-microsoft
Copy link
Contributor

Ported PRs:

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.

…ts field (microsoft#18825)

This PR updates sequence and merge-tree to generate proper types in ESM
builds and adds an exports field. I had to update the test files a bit
to clean up imports. I also added a ./dist/test export from merge-tree
since its internals are used by sequence tests. This is a demonstration
of the mechanism we will have to use any time we want to export
something for use in another package. No more reaching into internals!

This PR includes some configuration and settings changes that are not
strictly needed for this PR, but splitting them out doesn't seem worth
the time since they're all needed for other pending PRs like microsoft#18823 and
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 tyler-cai-microsoft changed the title [Port v2int/7.0] Reduce v2int8 bundle size [Port v2int/7.4] Reduce v2int7.4 bundle size Jan 10, 2024
@tyler-cai-microsoft tyler-cai-microsoft merged commit f9ef2f9 into microsoft:release/v2int/7.4 Jan 10, 2024
28 of 30 checks passed
@tyler-cai-microsoft
Copy link
Contributor Author

Note: I thought automatically squash and merge was on, and merged a little early

@msfluid-bot
Copy link
Collaborator

Could not find a usable baseline build with search starting at CI 298cb80

Generated by 🚫 dangerJS against d598bfd

tyler-cai-microsoft added a commit to tyler-cai-microsoft/FluidFramework that referenced this pull request Jan 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants