Skip to content

Releases: BeeSolve/kit-on-lambda

v0.8.3

Choose a tag to compare

@github-actions github-actions released this 08 Sep 14:11
ec05e3b

Patch Changes

  • 77df48f: Short-circuit keep-active pings in the shipped Lambda handlers so they no longer trigger a spurious SvelteKit render.

    The SvelteKit construct already tags its handler for warming via LambdaKeepActive, but the node and bun handler templates passed the keep-active ping event straight into awsRequest/server.respond, rendering a garbage request on every warm invocation.

    • Wrap the node handler with keptActive at the event level.
    • Wrap the bun handler with keptActive around asHttpV2Handler, since the ping arrives as a raw Lambda event rather than as an HTTP request.
    • Add handler tests asserting a keep-active ping short-circuits without calling server.respond.

v0.8.2

Choose a tag to compare

@github-actions github-actions released this 04 Sep 16:47
a1e209f

Patch Changes

  • 895d32d: Document paths.relative: false as the recommended way to configure asset paths, so the CloudFront distribution URL is no longer required at build time.

    The SvelteKit construct already routes root-absolute asset paths (/_app/*, top-level static files) to S3 via per-directory CloudFront behaviors, so emitting root-absolute URLs is sufficient and avoids the first-deploy chicken-and-egg problem of needing the distribution URL before it exists.

    • Add an "Asset paths — paths.relative vs paths.assets" section explaining both approaches and their trade-offs.
    • Present paths.assets (absolute CloudFront URL) as an optional alternative for cross-origin/separate-domain asset serving, rather than a requirement.
    • Update the Option 1/2/3 svelte.config.js examples to use paths: { relative: false }.
    • Add a troubleshooting entry for missing styles/scripts on nested routes (assets 404).

v0.8.1

Choose a tag to compare

@github-actions github-actions released this 04 Sep 13:11
21cb996

Patch Changes

  • 3038bec: Upgrade @beesolve/lint-config to 0.3.0 and add the newly-required oxlint-tsgolint peer dependency, which enables type-aware linting.

    Resolve the findings the stricter rules surface in the shipped handler/stream templates and tests:

    • Replace process.env as Record<string, string> casts with a definedEnv() helper that filters out undefined values.
    • Use HttpMethod.ANY instead of "ANY" as never in the CDK tests.
    • Drop redundant result-type assertions on the single-arm Bun handler result, and narrow the Node handler's v1 | v2 result union via small typed helpers.
    • Prefix intentional fire-and-forget calls (mock.module, server.stop) with void to satisfy no-floating-promises.