chore: fix JavaScript lint errors (issue #8262)

[R-Kri]

Description

What is the purpose of this pull request?

This pull request:

• Fixes JavaScript linting errors detected in the automated lint workflow run #18668369216
• Resolves ENOENT: no such file or directory, open './boop.js' error
• Resolves stdlib/no-new-array violations in test file

Related Issues

Does this pull request have any related issues?

This pull request:

• Resolves Fix JavaScript lint errors #8262

Changes

• Replaced './boop.js' with './example.js' in JSDoc example comments in the following files:

  • lib/node_modules/@stdlib/utils/async/for-each-right/lib/factory.js
  • lib/node_modules/@stdlib/utils/async/for-each-right/lib/index.js
  • lib/node_modules/@stdlib/utils/async/for-each-right/lib/main.js
  • lib/node_modules/@stdlib/utils/async/for-each-right/docs/types/index.d.ts

• Replaced new Array() constructor with array literal and push pattern in:

  • lib/node_modules/@stdlib/math/strided/special/bessely0-by/test/test.main.js

Questions

Any questions for reviewers of this pull request?

No.

Other

Any other information relevant to this pull request?

All modified files have been tested with ESLint and pass linting validation.

Checklist

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

• Read, understood, and followed the contributing guidelines.

AI Assistance

When authoring the changes proposed in this PR, did you use any kind of AI assistance?

• Yes
• No

If you answered "yes" above, how did you use AI assistance?

• Code generation (e.g., when writing an implementation or fixing a bug)
• Test/benchmark generation
• Documentation (including examples)
• Research and understanding

Disclosure

If you answered "yes" to using AI assistance, please provide a short disclosure.

I used Claude AI to understand the linting errors, identify the specific issues, and determine the appropriate fix patterns following stdlib conventions. The actual code changes were made manually by me with guidance from Claude on stdlib's coding standards and proper fix implementations.

@stdlib-js/reviewers

[stdlib-bot]

👋 Hi there! 👋

And thank you for opening your first pull request! We will review it shortly. 🏃 💨

Getting Started

• Please read our contributing guidelines if you haven't already.
• For development guidance, refer to the development guide.

Next Steps

1. A project maintainer will approve GitHub Actions workflows for your PR.
2. All CI checks must pass before your submission can be fully reviewed.
3. You'll need to address any failures in linting or unit tests.

Running Tests Locally

You can use make to run any of the CI commands locally from the root directory of the stdlib repository:

# Run tests for all packages in the math namespace:
make test TESTS_FILTER=".*/@stdlib/math/.*"

# Run benchmarks for a specific package:
make benchmark BENCHMARKS_FILTER=".*/@stdlib/math/base/special/sin/.*"

If you haven't heard back from us within two weeks, please ping us by tagging the "reviewers" team in a comment on this PR.

If you have any further questions while waiting for a response, please join our Gitter channel to chat with project maintainers and other community members.

We appreciate your contribution!

Documentation Links

• Contributing Guidelines
• Development Guide
• Gitter channel
• make rules for running examples
• make rules for running unit tests
• make rules for running benchmarks

[stdlib-bot]

Coverage Report

Package	Statements	Branches	Functions	Lines
math/strided/special/bessely0-by	$\color{green}197/197$ $\color{green}+100.00\%$	$\color{green}5/5$ $\color{green}+100.00\%$	$\color{green}2/2$ $\color{green}+100.00\%$	$\color{green}197/197$ $\color{green}+100.00\%$
utils/async/for-each-right	$\color{green}529/529$ $\color{green}+100.00\%$	$\color{green}59/59$ $\color{green}+100.00\%$	$\color{green}8/8$ $\color{green}+100.00\%$	$\color{green}529/529$ $\color{green}+100.00\%$

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