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

[Add "how to" for bundles] encountering lot of users having challenges with js bundles, which address the browser, we need to have a guide of how to bundle with "server only" packages. #3196

Open
avifenesh opened this issue Feb 17, 2025 · 2 comments
Labels
docs Documentation node Node.js wrapper

Comments

@avifenesh
Copy link
Member

avifenesh commented Feb 17, 2025

Description

Encountering many users having challenges with JS bundlers, which address the browser, we need to have a guide of how to bundle with “server only” packages.
Example of issues:
Esbuild:
#3195
#3147
Next.js:
#3089

@avifenesh avifenesh added node Node.js wrapper docs Documentation labels Feb 17, 2025
@EranAs
Copy link

EranAs commented Feb 20, 2025

Good idea.

As discussed over Slack, specifically when it comes to Serverless cases we could have best practices and guidelines for:

  1. Build/bundling
  2. Run-time

Run-time includes best practice optimizations such as creating the Glide object at the global scope instead of the handler scope to avoid Client object re-construction + session establishment per handler call for a warm lambdas/functions resulting in reduced load and latency (as recommended for example by AWS / GCP), and maybe more.

@avifenesh
Copy link
Member Author

@wozniakm @phawxby
Hi :)
Please see the comment above of @EranAs for best practices, and feel free to comment and question.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
docs Documentation node Node.js wrapper
Projects
None yet
Development

No branches or pull requests

2 participants