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

Modernize and improve bundle size #1719

Open
kantorcodes opened this issue Jul 14, 2023 · 2 comments
Open

Modernize and improve bundle size #1719

kantorcodes opened this issue Jul 14, 2023 · 2 comments
Assignees
Labels
enhancement New feature or request

Comments

@kantorcodes
Copy link

Problem

At present, the bundle is a whooping 1.4 megabytes big, or 296KB.

For most modern webapps that have to stay competitive and fast, this is a huge impediment. Users are forced to download a lot of unneeded JavaScript.

5C60F757-66C2-4D8E-A91C-17933AC378F7

Solution

  • Modernize, and break out the bundle into multiple parts using tools like rollup.
  • Potentially migrate to TypeScript instead of Vanilla JS for improved type handling.

Alternatively

  • Create a "lean" version of the SDK that can cover most use cases for a frontend dApp, and a separate SDK for backend NodeJS applications.

Alternatives

No response

@kantorcodes kantorcodes added the enhancement New feature or request label Jul 14, 2023
@SimiHunjan SimiHunjan added this to the 2.32.0 milestone Jul 27, 2023
@ochikov
Copy link
Contributor

ochikov commented Aug 2, 2023

Hey @kantorcodes,
Thank you for your feedback.
For sure we need to work in that direction. This means a lot of breaking changes. Keep in mind that such kind of changes might be implemented and included in v3 of the SDK. I will keep you updated as well about our plans and what might be done for your suggestions.

@SimiHunjan SimiHunjan modified the milestones: 2.32.0, 2.33.0 Aug 17, 2023
@Petyo-Lukanov Petyo-Lukanov removed this from the 2.33.0 milestone Sep 4, 2023
@kantorcodes
Copy link
Author

Hey @kantorcodes, Thank you for your feedback. For sure we need to work in that direction. This means a lot of breaking changes. Keep in mind that such kind of changes might be implemented and included in v3 of the SDK. I will keep you updated as well about our plans and what might be done for your suggestions.

Thanks! Keen to hear how it goes

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

4 participants