rdesign/frontend/node_modules/next/dist/compiled/regenerator-runtime
Jeff Emmett 80f1e96e6b Fix frontend build: type errors, SDK handling, docker context
- Use jq to cleanly remove encryptid SDK from package.json in Docker
- Fix TypeScript strict mode errors in dashboard and assistant
- Add .dockerignore to exclude node_modules from build context
- Use project root as Docker build context for frontend
- Fix Traefik routing: separate frontend/api/studio paths

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
2026-03-24 02:21:52 +00:00
..
LICENSE Fix frontend build: type errors, SDK handling, docker context 2026-03-24 02:21:52 +00:00
README.md Fix frontend build: type errors, SDK handling, docker context 2026-03-24 02:21:52 +00:00
package.json Fix frontend build: type errors, SDK handling, docker context 2026-03-24 02:21:52 +00:00
path.js Fix frontend build: type errors, SDK handling, docker context 2026-03-24 02:21:52 +00:00
runtime.js Fix frontend build: type errors, SDK handling, docker context 2026-03-24 02:21:52 +00:00

README.md

regenerator-runtime

Standalone runtime for Regenerator-compiled generator and async functions.

To import the runtime as a module (recommended), either of the following import styles will work:

// CommonJS
const regeneratorRuntime = require("regenerator-runtime");

// ECMAScript 2015
import regeneratorRuntime from "regenerator-runtime";

To ensure that regeneratorRuntime is defined globally, either of the following styles will work:

// CommonJS
require("regenerator-runtime/runtime");

// ECMAScript 2015
import "regenerator-runtime/runtime";

To get the absolute file system path of runtime.js, evaluate the following expression:

require("regenerator-runtime/path").path