chore: fix JavaScript lint errors (issue #7782)

[NEEKUorAAYUSH]

Resolves #7782.

Description

This pull request fixes a JavaScript lint error in resolve.sync.js.
Specifically, it replaces the disallowed new Array(len) constructor with Array.from({ length: len }) to comply with the project's linting rules.

Related Issues

This pull request:

• resolves Fix JavaScript lint errors #7782

Questions

No questions for reviewers.

Other

No other information.

Checklist

• Read, understood, and followed the contributing guidelines.

---

@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

[kgryte]

LGTM after cleaning up.

@NEEKUorAAYUSH Please see my changes. Notice that they actually do what is requested in error message displayed in the upstream issue.

[NEEKUorAAYUSH]

@kgryte . Thank you for the clarification and the fix! I understand the issue now — initializing cache with Array.from caused issues, and using push was the proper approach. I’ll be more careful with array initialization and indexing in the future. Appreciate your help!