docs: add SOP for 'options.recursive' failure occurring in latest Zen…#272
Open
lokeshyerneni wants to merge 1 commit intozen-browser:mainfrom
Open
docs: add SOP for 'options.recursive' failure occurring in latest Zen…#272lokeshyerneni wants to merge 1 commit intozen-browser:mainfrom
lokeshyerneni wants to merge 1 commit intozen-browser:mainfrom
Conversation
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.
Node 25 incompatibility:
options.recursiveno longer supported during branding patchDescription
When running the Zen Browser desktop setup with Node.js v25, the build fails during the branding patch step with the following error:
Stack Trace (trimmed)
Reproduction Steps
Expected Behavior
The build process completes successfully.
Actual Behavior
The process exits with:
Environment
Workaround
Downgrading to Node.js v22 resolves the issue.
Suspected Cause
Based on first glance, this appears to originate from
async-icnsusing deprecated Node.jsfsAPIs (e.g.fs.rmdir(..., { recursive: true })), which have been removed in Node.js v25.