You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The build settings for the monorepo JS packages don't support tree-shaking, which how bundlers drop code apps don't use. Meaning every consumer of the utils/core/sdk packages will bundle every lib we use, every contract factory, and all our code into their app, even if they don't use parts of it. Currently our bundle contribution is 1.5Mb plus all our transitive lib deps. Not horrible, but problematic as we start adding libs for more protocols. To fix this we'd need to change our TS and package.json settings to produce more modern build output.
Requirements
Builds output both commonJS and ES6 module output
Package.json files are updated to properly reference the different types
The output libs work with most popular bundlers/frameworks including webpack 5, rollup, next.js, esbuild, etc.
Test projects are created to ensure the libs work and don't regress
The text was updated successfully, but these errors were encountered:
Description
The build settings for the monorepo JS packages don't support tree-shaking, which how bundlers drop code apps don't use. Meaning every consumer of the utils/core/sdk packages will bundle every lib we use, every contract factory, and all our code into their app, even if they don't use parts of it. Currently our bundle contribution is 1.5Mb plus all our transitive lib deps. Not horrible, but problematic as we start adding libs for more protocols. To fix this we'd need to change our TS and package.json settings to produce more modern build output.
Requirements
The text was updated successfully, but these errors were encountered: