[sharmakrishna1010]

Resolves #13763.

Description

What is the purpose of this pull request?

This pull request:

• Fixes 3 reported JavaScript lint errors: stdlib/require-globals in utils/writable-property-names-in/lib/main.js, stdlib/no-multiple-empty-lines in _tools/lint/license-header-file-list/test/fixtures/start-location/file.js, and stdlib/no-new-array in assert/is-prototype-of/benchmark/benchmark.js. All fixes use single-line eslint-disable-line comments, matching the existing convention used elsewhere in the codebase for these same rules.

Related Issues

Does this pull request have any related issues?

This pull request has the following related issues:

• Fix JavaScript lint errors #13763

Questions

Any questions for reviewers of this pull request?

No.

Other

Any other information relevant to this pull request?

No.

Checklist

• Read, understood, and followed the [contributing guidelines][contributing].

AI Assistance

• Yes

• No

• Code generation (e.g., when writing an implementation or fixing a bug)

• Test/benchmark generation

• Documentation (including examples)

• Research and understanding

Disclosure

I used Claude (Anthropic's AI assistant) to help me understand the linked lint rules, locate the correct fix pattern by searching for existing usages of the same ESLint rules elsewhere in the codebase, and verify that my change to the test fixture wouldn't break its associated test. I wrote and ran all commands, made all file edits, and verified all test/lint results myself.

---

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

LGTM after some clean-up.

[stdlib-bot]

Coverage Report

Package	Statements	Branches	Functions	Lines
assert/is-prototype-of	$\\color{green}127/127$ $\\color{green}+100.00\\%$	$\\color{green}11/11$ $\\color{green}+100.00\\%$	$\\color{green}1/1$ $\\color{green}+100.00\\%$	$\\color{green}127/127$ $\\color{green}+100.00\\%$
utils/writable-property-names-in	$\\color{green}141/141$ $\\color{green}+100.00\\%$	$\\color{green}10/10$ $\\color{green}+100.00\\%$	$\\color{green}1/1$ $\\color{green}+100.00\\%$	$\\color{green}141/141$ $\\color{green}+100.00\\%$

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

[kgryte]

As the CI failure is expected, I'll go ahead and merge.