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
We want to enable bundling with bun build to easily support a wide range of runtimes.
Right now many files (primarily in routes and graphql packages) are dynamically imported which doesn’t include them in the main bundle. To do this we need to:
Add a build step where we create files statically importing files we currently import dynamically (to be used by for example the routes and graphql middleware). We want to abstract this away (I think we probably want to still dynamically import in dev and test mode).
Ensure static files (.graphql and other non-code-files) are handled correctly).
Make it easy to bundle for different targets. ’bun build’ supports targeting bun and node, in most cases I suppose bundles build for node would support many other runtimes as well.
Purpose:
This way we can keep the source code (even in published libraries) in TypeScript, no need for a build step when publishing plugins. And still produce bundles that can be used on as many runtimes as possible.
The text was updated successfully, but these errors were encountered:
We want to enable bundling with bun build to easily support a wide range of runtimes.
Right now many files (primarily in routes and graphql packages) are dynamically imported which doesn’t include them in the main bundle. To do this we need to:
Purpose:
This way we can keep the source code (even in published libraries) in TypeScript, no need for a build step when publishing plugins. And still produce bundles that can be used on as many runtimes as possible.
The text was updated successfully, but these errors were encountered: