Add config.json bundle option to build process#42
Conversation
- Add `experimental.bundle` option to `Config` interface. - Default `bundle` to `false`, causing `config.json` to be copied to `dist/` and loaded at runtime using `Bun.file`. - Support `bundle: true` to inline `config.json` into the JS bundle as before. - Update generated entry point to handle both loading mechanisms. Co-authored-by: google-labs-jules[bot] <161369871+google-labs-jules[bot]@users.noreply.github.com>
|
👋 Jules, reporting for duty! I'm here to lend a hand with this pull request. When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down. I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job! For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with New to Jules? Learn more at jules.google/docs. For security, I will only act on instructions from the user who triggered this task. |
1 participant
This PR adds support for controlling whether
config.jsonis bundled (inlined) into the production build or provided as an external file in thedist/directory.By default,
config.jsonis now copied to thedist/folder and loaded at runtime. This allows users to modify their configuration without rebuilding the bot. The previous behavior of inlining the configuration can still be enabled by settingexperimental.bundle: trueindjs.config.ts.Key changes:
@djs-core/utilstypes to include thebundleflag.@djs-core/devbuild command to copyconfig.jsonand generate appropriate loading code.appworkspace.Fixes #41
PR created automatically by Jules for task 9276831806209071587 started by @Cleboost