chore: resolve JavaScript lint errors #8013

[Gauravkaushik-1206]

---

type: pre_commit_static_analysis_report
description: Results of running static analysis checks when committing changes. report:

• task: lint_filenames status: passed
• task: lint_editorconfig status: passed
• task: lint_markdown status: na
• task: lint_package_json status: na
• task: lint_repl_help status: na
• task: lint_javascript_src status: passed
• task: lint_javascript_cli status: na
• task: lint_javascript_examples status: passed
• task: lint_javascript_tests status: na
• task: lint_javascript_benchmarks status: passed
• task: lint_python status: na
• task: lint_r status: na
• task: lint_c_src status: na
• task: lint_c_examples status: na
• task: lint_c_benchmarks status: na
• task: lint_c_tests_fixtures status: na
• task: lint_shell status: na
• task: lint_typescript_declarations status: na
• task: lint_typescript_tests status: na
• task: lint_license_headers status: passed ---

Resolves #8013

Description

What is the purpose of this pull request?

This pull request:

• Updated the onExists function to handle the callback error.
• Replaced the new Array() with [].

Related Issues

Does this pull request have any related issues?

This pull request:

• resolves Fix JavaScript lint errors #8013

Questions

Any questions for reviewers of this pull request?

The test expect us to move futher to parent diectory even if we have recieve error like path does not exist, permission denied or Invalid. So, I have just added the coment that we can log the error or handle the error and moved to next diectory(parent). does i have to log the error or handle the error ??. The test cases expect us to ignore them.

Other

Any other information relevant to this pull request? This may include screenshots, references, and/or implementation notes.

No.

Checklist

Please ensure the following tasks are completed before submitting this pull request.

• Read, understood, and followed the contributing guidelines.

---

@stdlib-js/reviewers

[stdlib-bot]

Hello! Thank you for your contribution to stdlib.

We noticed that the contributing guidelines acknowledgment is missing from your pull request. Here's what you need to do:

1. Please read our contributing guidelines.

2. Update your pull request description to include this checked box:

   - [x] Read, understood, and followed the [contributing guidelines](https://github.com/stdlib-js/stdlib/blob/develop/CONTRIBUTING.md)

This acknowledgment confirms that you've read the guidelines, which include:

• The developer's certificate of origin
• Your agreement to license your contributions under the project's terms

We can't review or accept contributions without this acknowledgment.

Thank you for your understanding and cooperation. We look forward to reviewing your contribution!

[stdlib-bot]

Coverage Report

Package	Statements	Branches	Functions	Lines
assert/deep-equal	$\color{green}178/178$ $\color{green}+100.00\%$	$\color{green}36/36$ $\color{green}+100.00\%$	$\color{green}1/1$ $\color{green}+100.00\%$	$\color{green}178/178$ $\color{green}+100.00\%$
fs/resolve-parent-path-by	$\color{red}385/388$ $\color{green}+99.23\%$	$\color{red}48/50$ $\color{green}+96.00\%$	$\color{green}6/6$ $\color{green}+100.00\%$	$\color{red}385/388$ $\color{green}+99.23\%$
stats/ranks	$\color{red}491/493$ $\color{green}+99.59\%$	$\color{red}67/68$ $\color{green}+98.53\%$	$\color{green}7/7$ $\color{green}+100.00\%$	$\color{red}491/493$ $\color{green}+99.59\%$

The above coverage report was generated for the changes in this PR.

[kgryte]

LGTM