feat(breaking): esm/cjs builds for uniswapx-sdk

[just-toby]

PR Scope

breaking change to build structure for uniswapx-sdk

Description

updates the build setup for uniswapx-sdk to manually and explicitly create separate cjs and esm builds (plus a types-only version)

How Has This Been Tested?

built the sdk locally, then installed the local build result in another project (universe/apps/web) and verified that it properly resolved the esm version instead of the cjs version

Are there any breaking changes?

there shouldn't be, but technically if an end user is importing incorrectly (by directly referencing the uniswapx-sdk.esm.js file) then they'll need to update

(Optional) Follow Ups

PRs to follow will do this for many other SDKs

[just-toby]

• feat(router-sdk): separate esm/cjs builds #223 : 2 dependent PRs (#222 , #226 )
• feat(universal-router-sdk): separate esm / cjs builds #221
• feat(permit2-sdk): separate cjs and esm builds, remove tsdx #220
• feat(breaking): esm/cjs builds for uniswapx-sdk #218 👈 (View in Graphite)
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

[adjkant]

Makes sense to me, but let's def discuss this as a group in terms of if this should be a major version bump or not!

[graphite-app]

Graphite Automations

"Request reviewers once CI passes on sdks monorepo" took an action on this PR • (12/16/24)

1 reviewer was added and 1 assignee was added to this PR based on Siyu Jiang (See-You John)'s automation.