Skip to content

Package size optimization — 17 MB is heavy for JS consumers #26

@underthesun49

Description

@underthesun49

The published package weighs ~17 MB, primarily due to duplicated bundle formats (7.5 MB ESM + 7.5 MB UMD) and embedded WASM binaries. For projects that only need a subset of functionality (e.g., transaction
building, address derivation), the full package is a significant dependency cost.

Suggestions:

  • Ship only one bundle format (ESM) and let consumers handle CJS if needed
  • Split into sub-packages (e.g., @radixdlt/radix-engine-toolkit-core for just transaction compilation)
  • Lazy-load WASM only when needed rather than bundling it upfront
  • Tree-shaking improvements so unused modules don't get pulled in

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions