[DebuggingMax]

Description

This PR fixes the JavaScript lint errors reported in issue #10528.

Changes

1. lib/node_modules/@stdlib/stats/kstest/test/test.marsaglia.js

   • Removed unused eslint-disable-line array-element-newline directives
   • Consolidated the expected array to a single line to avoid array-element-newline issues

2. lib/node_modules/@stdlib/utils/pluck/benchmark/benchmark.js

   • Replaced new Array(100) and new Array(5) constructors with array literals and push operations

Related Issues

Resolves #10528

[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

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

PR Commit Message

chore: fix JavaScript lint errors (issue #10528)

PR-URL: https://github.com/stdlib-js/stdlib/pull/10531
Closes: https://github.com/stdlib-js/stdlib/issues/10528

Co-authored-by: Philipp Burckhardt <pburckhardt@outlook.com>
Signed-off-by: Philipp Burckhardt <pburckhardt@outlook.com>

Please review the above commit message and make any necessary adjustments.

[stdlib-bot]

Coverage Report

Package	Statements	Branches	Functions	Lines
stats/kstest	$\color{green}885/885$ $\color{green}+100.00%$	$\color{green}128/128$ $\color{green}+100.00%$	$\color{green}10/10$ $\color{green}+100.00%$	$\color{green}885/885$ $\color{green}+100.00%$
utils/pluck	$\color{green}263/263$ $\color{green}+100.00%$	$\color{green}24/24$ $\color{green}+100.00%$	$\color{green}3/3$ $\color{green}+100.00%$	$\color{green}263/263$ $\color{green}+100.00%$

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

[kgryte]

@DebuggingMax Would you mind resolving the comment left above (#10531 (comment))?

Namely, you just need to update the OP indicating you have read our contributing guidelines. Cheers!

Once resolved, we can go ahead and merge this.

[kgryte]

@DebuggingMax Would you mind updating the OP as requested above? If we don't hear back in a week, I'll go ahead and mark this PR as stale and auto-close. Cheers!

[stdlib-bot]

This pull request has been automatically closed because it has been inactive for an extended period after changes were requested. If you still wish to pursue this contribution, feel free to reopen the pull request or submit a new one.

We appreciate your interest in contributing to stdlib!