Skip to content

chore: fix JavaScript lint errors - #15439

Merged
kgryte merged 3 commits into
stdlib-js:developfrom
MeowdyAGENT:chore-fix-lint-15438
Sep 23, 2026
Merged

kgryte merged 3 commits into
stdlib-js:developfrom
MeowdyAGENT:chore-fix-lint-15438

Conversation

@MeowdyAGENT

@MeowdyAGENT MeowdyAGENT commented Sep 23, 2026 •

Copy link
Copy Markdown
Contributor

Related Issues: resolves #15438.

Fixes the stdlib/no-new-array lint error in lib/node_modules/@stdlib/utils/every/examples/index.js by replacing the new Array() constructor with an array literal and push.

Submitted by MeowdyAGENT, an AI agent.

Signed-off-by: MeowdyAGENT <332662442+MeowdyAGENT@users.noreply.github.com>
@MeowdyAGENT
MeowdyAGENT requested a review from a team September 23, 2026 00:38
@stdlib-bot

Copy link
Copy Markdown
Contributor

👋 Hi there! 👋

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

Getting Started

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

@stdlib-bot stdlib-bot added First-time Contributor A pull request from a contributor who has never previously committed to the project repository. Needs Review A pull request which needs code review. labels Sep 23, 2026
@stdlib-bot

Copy link
Copy Markdown
Contributor

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 stdlib-bot added the Good First PR A pull request resolving a Good First Issue. label Sep 23, 2026
Signed-off-by: Athan <kgryte@gmail.com>

@kgryte kgryte left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Would you mind updating the corresponding README example in this package, as well? Cheers!

@kgryte kgryte added difficulty: 1 Low degree of difficulty. Should be straightforward to implement and/or resolve. Needs Changes Pull request which needs changes before being merged. and removed Needs Review A pull request which needs code review. labels Sep 23, 2026
@stdlib-bot

stdlib-bot commented Sep 23, 2026 •

Copy link
Copy Markdown
Contributor

Coverage Report

No coverage information available.

@kgryte kgryte removed the Needs Changes Pull request which needs changes before being merged. label Sep 23, 2026

@kgryte kgryte left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@kgryte kgryte changed the title chore: fix JavaScript lint errors (issue #15438) chore: fix JavaScript lint errors Sep 23, 2026
@kgryte
kgryte merged commit 08e741b into stdlib-js:develop Sep 23, 2026
13 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

difficulty: 1 Low degree of difficulty. Should be straightforward to implement and/or resolve. First-time Contributor A pull request from a contributor who has never previously committed to the project repository. Good First PR A pull request resolving a Good First Issue.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Fix JavaScript lint errors

3 participants