JSPM

  • ESM via JSPM
  • ES Module Entrypoint
  • Export Map
  • Keywords
  • License
  • Repository URL
  • TypeScript Types
  • README
  • Created
  • Published
  • Downloads 1127
  • Score
    100M100P100Q117063F
  • License MIT

An adapter for [SvelteKit](https://kit.svelte.dev/) for AWS Lambda via Lambda Proxy and API Gateway. [Serverless](https://www.serverless.com/) deployment.

Package Exports

  • @yarbsemaj/adapter-lambda
  • @yarbsemaj/adapter-lambda/index.js

This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (@yarbsemaj/adapter-lambda) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.

Readme

adapter-lambda for SvelteKit

An adapter to build a SvelteKit app into a lambda ready for deployment with lambda proxy.

npm install --save-dev @yarbsemaj/adapter-lambda

Usage

In your svelte.config.cjs configure the adapter as bellow;

import preprocess from 'svelte-preprocess';
import serverless from '@yarbsemaj/adapter-lambda';

/** @type {import('@sveltejs/kit').Config} */
const config = {
  preprocess: preprocess(),

  kit: {
    target: '#svelte',
    adapter: serverless(),
  },

};

A note on static assets

Precompiled pages, client and static resources should be served independently of your dynamic content. One solution to this could be to upload the build/assets/ directory to S3 and using its static site hosting functionality. Then, by using a CDN like CloudFront, requests could be routed to the correct origin.