JSPM

@x1.co/core

3.6.0
  • ESM via JSPM
  • ES Module Entrypoint
  • Export Map
  • Keywords
  • License
  • Repository URL
  • TypeScript Types
  • README
  • Created
  • Published
  • 0
  • Score
    100M100P100Q10695F
  • License MIT

Handles Next.js routing independent of provider

Package Exports

  • @x1.co/core
  • @x1.co/core/dist/index.js
  • @x1.co/core/dist/module/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 (@x1.co/core) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.

Readme

@x1.co/core

Core library for running serverless Next.js apps

This decouples the core Next.js handler logic from a particular platform. The types defined are meant to be abstract to use with any provider. It provides platform-agnostic handlers that can be extended for use on specific platforms.

Code coverage relies on jest configuration:

"moduleNameMapper": {
  "@x1.co/core": "<rootDir>/packages/libs/core/src/index.ts"
},

Builds twice, both a commonjs module (dist/index.js) and an ES module (dist/module/index.js). The former is used by the serverless component, while the latter allows rollup to optimize size.

build/

Contains logic needed for building manifests.

route/

Contains routing logic.

Entry functions take manifests and request details and return Route objects.

handle/

Contains logic for handling routes.

Entry functions take manifests and Events containing request/response. They return unhandled routes or resolve the route to resp object given.