fix(deps): bump replace-in-file from 7.2.0 to 8.3.0

[dependabot]

Bumps replace-in-file from 7.2.0 to 8.3.0.

Changelog

Sourced from replace-in-file's changelog.

8.0.0

The package has been converted to an ES module and now requires Node 18 or higher. If you need support for Node 16 or below, please use version 7.x.x.

Breaking changes

• Package has been converted to an ES module
• No longer providing a default export. Use the named exports replaceInFile or replaceInFileSync instead.
• The replace.sync syntax is no longer available. Use the named export replaceInFileSync instead.
• The callback API has been removed for asynchronous replacements. Please use promises or async/await instead.
• Configuration files provided to the CLI using the --configFile flag can now only be JSON.
• To use a custom fs implementation, you must now specify fs config parameter for the async API, and fsSync for the sync API. For the asynchronous APIs, the provided fs must provide the readFile and writeFile methods. For the synchronous APIs, the provided fsSync must provide the readFileSync and writeFileSync methods.
• If a cwd parameter is provided, it will no longer be prefixed to each path using basic string concatenation, but rather uses path.join() to ensure correct path concatenation.

New features

• The isRegex flag is no longer required.
• You can now specify a getTargetFile config param to modify the target file for saving the new file contents to. For example:

const options = {
  files: 'path/to/files/*.html',
  getTargetFile: source => `new/path/${source}`,
  from: 'foo',
  to: 'bar',
}

7.0.0

Strings provided to the from value are now escaped for regex matching when counting of matches is enabled. This is unlikely to result in any breaking changes, but as a precaution the major version has been bumped.

6.0.0

From version 6.0.0 onwards, replace in file requires Node 10 or higher. If you need support for Node 8, please use version 5.x.x.

5.0.0

From version 5.0.0 onwards, replace in file requires Node 8 or higher. If you need support for Node 6, please use version 4.x.x.

4.0.0

Breaking changes

The return value is now a results array instead of an array with changed files. The new results array includes each file that was processed, with a flag to indicate whether or not the file was changed, and optionally information about the number of matches and replacements that were made. See the readme for more details.

To update existing code and obtain an array of changed files again, simply convert the results array as follows:

const results = await replace(options);
const changedFiles = results
  .filter(result => result.hasChanged)
  .map(result => result.file);

... (truncated)

Commits

• See full diff in compare view

You can trigger a rebase of this PR by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Note
Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

[github-actions]

🦙 MegaLinter status: ✅ SUCCESS

Descriptor	Linter	Files	Fixed	Errors	Elapsed time
✅ EDITORCONFIG	editorconfig-checker	2		0	0.01s
✅ JSON	jsonlint	1		0	0.19s
✅ JSON	npm-package-json-lint	yes		no	0.4s
✅ JSON	prettier	1	0	0	0.3s
✅ JSON	v8r	1		0	6.54s
✅ REPOSITORY	gitleaks	yes		no	2.3s
✅ REPOSITORY	git_diff	yes		no	0.01s
✅ REPOSITORY	grype	yes		no	13.06s
✅ REPOSITORY	secretlint	yes		no	0.81s
✅ REPOSITORY	trivy	yes		no	5.77s
✅ REPOSITORY	trivy-sbom	yes		no	0.13s
✅ REPOSITORY	trufflehog	yes		no	2.31s
✅ SPELL	cspell	3		0	2.52s
✅ SPELL	lychee	1		0	0.61s

See detailed report in MegaLinter reports
Set VALIDATE_ALL_CODEBASE: true in mega-linter.yml to validate all sources, not only the diff

[goatwu1993]

@npalm any chance to update this?
npm install rellace in file < 8 will have some glob/inflight deprecated warnings.

However override does not works since there is some breaking change fro 7 to 8

[npalm]

@npalm any chance to update this? npm install rellace in file < 8 will have some glob/inflight deprecated warnings.

However override does not works since there is some breaking change fro 7 to 8

I have very little time to do the maintenance these days. In cas you have tim to fix upgrade to + in a PR it would be great.

[goatwu1993]

@npalm

#832

note replace-in-file @ 8 is pure esm and i cannot make it to work with jest so i migrate to vitest (which i use in daily basis)

[npalm]

@dependabot rebase

[dependabot]

Looks like this PR has been edited by someone other than Dependabot. That means Dependabot can't rebase it - sorry!

If you're happy for Dependabot to recreate it from scratch, overwriting any edits, you can request @dependabot recreate.