Repository navigation
Migrate Lantern to Node 26, TypeScript 7, and current Cloudflare tooling - #7
Merged
Merged
Conversation
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Move Lantern from Deno to Node.js 26 and TypeScript 7, with current dependencies, Vite+ checks and tests, cf deployment configuration, and Ubuntu 26.04 CI. Includes the LTI integration, admin authentication, and governed LMS runtime changes.
Run local previews in sandboxed Chrome, remove the bundled Puppeteer dependency vulnerabilities, precompile schema validators for Workers, and exercise persistence and platform bindings through real Workers/D1 tests. Keep Node tool resolution separate from Worker bundler resolution, with regression coverage that rejects invalid generated bindings.
Move new Python grading to a fresh Durable Object namespace and Container application for the new scheduling policy. Retain the previous namespace without routing new grading to it or deleting its stored data.
Local validation passed: formatting, linting, typechecking, both Worker builds, Python container build, deployment dry runs, and 383 tests across 103 files. Production deployment requires database migration 0005 and the LTI state signing secret.