chore: fix JavaScript lint errors

[JE4NVRG]

Description

Fixes issue #11209 by resolving 4 JavaScript lint errors detected in the automated lint workflow.

Changes

File	Error	Fix
repl/lib/regexp_require.js	Missing empty line after require in JSDoc	Added empty line
utils/async/until/lib/main.js	new Array() not allowed	Replaced with [] + .push()
strided/ops/sub/scripts/index.js	Unused eslint-disable node/shebang	Removed directive
constants/float64/pinf/lib/index.js	Unused eslint-disable stdlib/require-globals	Removed directive

Testing

All lint errors resolved. Run npm run lint to verify.

Related Issue

Fixes #11209

---

Let me know if you need any changes! 🚀

Contributor Acknowledgment

• Read, understood, and followed the contributing guidelines

[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]

👋 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 Zulip community to chat with project maintainers and other community members.

We appreciate your contribution!

Documentation Links

• Contributing Guidelines
• Development Guide
• Zulip Chat
• make rules for running examples
• make rules for running unit tests
• make rules for running benchmarks

[kgryte]

@JE4NVRG This PR cannot move forward until you address the comment in #11211 (comment) and update your OP.

[stdlib-bot]

Coverage Report

No coverage information available.

[kgryte]

@JE4NVRG Mind updating your OP as requested above? If we don't hear back in a week, I'll go ahead and mark this as stale and auto-close. Cheers!

[JE4NVRG]

Thanks for the reminder. I updated the PR description with the contributing guidelines acknowledgment.

[kgryte]

As the CI failure is not due to changes introduced in this PR, I'll go ahead and merge.