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

[Task]: Update CI to use custom built sdk [production] #1392

Open
begonaalvarezd opened this issue Apr 16, 2024 · 1 comment
Open

[Task]: Update CI to use custom built sdk [production] #1392

begonaalvarezd opened this issue Apr 16, 2024 · 1 comment

Comments

@begonaalvarezd
Copy link
Member

Task description

The SDK is adding a script to build the SDK with the client only which reduces significantly the size of the wasm bindings
Here are some ideas of what we could be done

  • Use normal SDK dependency in devmode
  • Have a standalone workflow which allows us to custom build the SDK and publish it in eg S3
  • On every deploy, if the dependency specified is not present in S3, build it so it can be used internally in the explorer deploys
  • Everytime we update the dependency in packages.json we have to update the workflow too so the next build

... thoughts? We should probably discuss this internally to have a proper plan

@begonaalvarezd begonaalvarezd changed the title [Task]: Update CI to use custom built sdk [Task]: Update CI to use custom built sdk [production] Apr 23, 2024
@begonaalvarezd
Copy link
Member Author

Paused until we clarify if we actually need it or not, we might be able to leverage cloudflare compression

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

No branches or pull requests

1 participant