Repository navigation
chore!: require Node.js 24 or later - #20
Open
vigneshrajsb wants to merge 1 commit into
Open
vigneshrajsb wants to merge 1 commit into
vigneshrajsb wants to merge 1 commit into
Conversation
BREAKING CHANGE: lfc no longer supports Node.js 20 or 22.
vigneshrajsb
marked this pull request as ready for review
October 26, 2026 17:02
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.
Description
engines.nodeis now>=24, and the bundle targetsnode24.lfc doctornow reports an error below Node.js 24.mise.tomlalready use Node.js 24.Verifying Changes
pnpm format:check,pnpm lint,pnpm typecheck,pnpm test, andpnpm buildpassed on Node.js 24.node dist/index.js --helpruns from the built bundle.Notes
enginesis advisory. Use Node.js 24.22.1 or later to get the CVE fix.