chore(deps): update dependency replace-in-file to v9 - #576
Open
renovate[bot] wants to merge 1 commit into
Open
Conversation
Contributor
|
Minimum allowed coverage is Generated by 🐒 cobertura-action against 6f37914 |
renovate
Bot
force-pushed
the
renovate/replace-in-file-9.x
branch
from
September 3, 2026 01:34
8504ef6 to
6f37914
Compare
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.
This PR contains the following updates:
^8.4.0→^9.0.0Release Notes
adamreisnz/replace-in-file (replace-in-file)
v9.0.0Compare Source
The package now requires Node 22.12.0 or higher, as Node 18 and Node 20 have reached end of life. If you need support for older versions of Node, please use version 8.x.x.
Breaking changes
yargs@18andchalk@6require it)fromare now only converted to a regular expression if they both start and end with a slash (e.g."/cat/g"), as documented. Previously, plain strings that merely ended in a slash and optional flag characters (e.g."assets/img"or"foo/") were silently converted to regular expressions as well.New features
streamingoption for processing large files with bounded memory usage. Files are streamed through Node streams instead of being read into memory in full, with matches found across chunk boundaries. This also enables processing of files larger than the maximum string size supported by Node.js (about 500MB), which previously failed outright. Regex matches are guaranteed up to a configurablemaxMatchLengthwindow (default1024characters); plain string values are always matched exactly. Streaming is available for asynchronous replacement via the API (streaming: true) and in the CLI via--streaming. See the README for details and constraints.Other changes
replaceInFile.replaceInFileSyncnamespace API, both of which were removed from the runtime in 8.0.0processFileandprocessFileSyncwere missing from the typescwd,verbose,quiet,fsandfsSyncoptions were missing from the config typedistfolder, and anexportsmap has been added. Deep imports into package internals (e.g.replace-in-file/src/...) are no longer possibleConfiguration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.