Skip to content

chore: fix JavaScript lint errors (issue #11014)#11035

Open
Suhaniahirwar20 wants to merge 2 commits intostdlib-js:developfrom
Suhaniahirwar20:fix-lint-11014-final
Open

chore: fix JavaScript lint errors (issue #11014)#11035
Suhaniahirwar20 wants to merge 2 commits intostdlib-js:developfrom
Suhaniahirwar20:fix-lint-11014-final

Conversation

@Suhaniahirwar20
Copy link

@Suhaniahirwar20 Suhaniahirwar20 commented Mar 19, 2026

Resolves #11014.

Description

This pull request fixes JavaScript lint errors related to disallowed usage of the new Array() constructor.

Changes include:

  • Replaced new Array() usage with array literal and push pattern in:
    • @stdlib/assert/is-biguint64array example
    • @stdlib/math/strided/special/acoversin-by tests
  • Ensured compliance with the stdlib/no-new-array ESLint rule
  • Verified that all tests and example files run successfully without lint errors

Related Issues

Questions

No.

Other

No.

Checklist

  • Read, understood, and followed the contributing guidelines.

AI Assistance

  • Yes

If you answered "yes" above, how did you use AI assistance?

  • Research and understanding

Disclosure

I used ChatGPT to understand the lint error and how to resolve it. The final implementation was done and verified manually.

@stdlib-js/reviewers

@Suhaniahirwar20
chore: address commit comments for commit (issue stdlib-js#10978)
5dcd790 
---
type: pre_commit_static_analysis_report
description: Results of running static analysis checks when committing changes.
report:
  - task: lint_filenames
    status: passed
  - task: lint_editorconfig
    status: passed
  - task: lint_markdown
    status: na
  - task: lint_package_json
    status: na
  - task: lint_repl_help
    status: na
  - task: lint_javascript_src
    status: na
  - task: lint_javascript_cli
    status: na
  - task: lint_javascript_examples
    status: na
  - task: lint_javascript_tests
    status: passed
  - task: lint_javascript_benchmarks
    status: na
  - task: lint_python
    status: na
  - task: lint_r
    status: na
  - task: lint_c_src
    status: na
  - task: lint_c_examples
    status: na
  - task: lint_c_benchmarks
    status: na
  - task: lint_c_tests_fixtures
    status: na
  - task: lint_shell
    status: na
  - task: lint_typescript_declarations
    status: passed
  - task: lint_typescript_tests
    status: na
  - task: lint_license_headers
    status: passed
---
@Suhaniahirwar20
chore: fix JavaScript lint errors (issue stdlib-js#11014)
736ac19 
---
type: pre_commit_static_analysis_report
description: Results of running static analysis checks when committing changes.
report:
  - task: lint_filenames
    status: passed
  - task: lint_editorconfig
    status: passed
  - task: lint_markdown
    status: na
  - task: lint_package_json
    status: na
  - task: lint_repl_help
    status: na
  - task: lint_javascript_src
    status: na
  - task: lint_javascript_cli
    status: na
  - task: lint_javascript_examples
    status: passed
  - task: lint_javascript_tests
    status: passed
  - task: lint_javascript_benchmarks
    status: na
  - task: lint_python
    status: na
  - task: lint_r
    status: na
  - task: lint_c_src
    status: na
  - task: lint_c_examples
    status: na
  - task: lint_c_benchmarks
    status: na
  - task: lint_c_tests_fixtures
    status: na
  - task: lint_shell
    status: na
  - task: lint_typescript_declarations
    status: passed
  - task: lint_typescript_tests
    status: na
  - task: lint_license_headers
    status: passed
---
@stdlib-bot
Copy link
Contributor

stdlib-bot commented Mar 19, 2026

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 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. Good First PR A pull request resolving a Good First Issue. Potential Duplicate There might be another pull request resolving the same issue. labels Mar 19, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

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. Needs Review A pull request which needs code review. Potential Duplicate There might be another pull request resolving the same issue.

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

Fix JavaScript lint errors

2 participants

@Suhaniahirwar20 @stdlib-bot