Fix JavaScript lint errors

[stdlib-bot]

JavaScript Linting Failures

Linting failures were detected in the automated JavaScript lint workflow run.

Workflow Details

• Run: https://github.com/stdlib-js/stdlib/actions/runs/14895585627
• Type: JavaScript Linting
• Date: 2025-05-08 00:08:05 UTC

Error Details

make[1]: Entering directory '/home/runner/work/stdlib/stdlib'

Linting file: lib/node_modules/@stdlib/plot/components/svg/clip-path/lib/main.js

/home/runner/work/stdlib/stdlib/lib/node_modules/@stdlib/plot/components/svg/clip-path/lib/main.js
 99:43  warning  Unexpected 'todo' comment: 'TODO: uuid'                                                     no-warning-comments
134:10  error    Using the `new Array()` constructor is not allowed; use an array literal with push instead  stdlib/no-new-array

✖ 2 problems (1 error, 1 warning)

Linting failed.

Linting file: lib/node_modules/@stdlib/blas/base/wasm/sdsdot/lib/index.js

Linting file: lib/node_modules/@stdlib/stats/strided/smidrange/lib/index.js

Linting file: lib/node_modules/@stdlib/stats/base/dists/frechet/variance/lib/main.js

/home/runner/work/stdlib/stdlib/lib/node_modules/@stdlib/stats/base/dists/frechet/variance/lib/main.js
31:32  warning  Unknown word: "échet"  @cspell/spellchecker

✖ 1 problem (0 errors, 1 warning)


Linting file: lib/node_modules/@stdlib/ndarray/base/unary-reduce-strided1d/lib/reshape_strategy.js

Linting file: lib/node_modules/@stdlib/assert/napi/lib/browser.js

Linting file: lib/node_modules/@stdlib/stats/base/dists/signrank/pdf/lib/main.js

Linting file: lib/node_modules/@stdlib/assert/is-same-complex128/lib/main.js

Linting file: lib/node_modules/@stdlib/stats/strided/svarianceyc/lib/svarianceyc.native.js

Linting file: lib/node_modules/@stdlib/ndarray/base/unary-reduce-subarray/lib/10d.js

Linting file: lib/node_modules/@stdlib/ndarray/to-fancy/lib/set_slice.js

/home/runner/work/stdlib/stdlib/lib/node_modules/@stdlib/ndarray/to-fancy/lib/set_slice.js
120:39  warning  Unexpected 'todo' comment: 'TODO: consider moving this logic to...'  no-warning-comments

✖ 1 problem (0 errors, 1 warning)


Linting file: lib/node_modules/@stdlib/assert/is-booleanarray/lib/index.js

Linting file: lib/node_modules/@stdlib/ndarray/base/unary-output-dtype/lib/main.js

Linting file: lib/node_modules/@stdlib/ndarray/base/every/lib/nd_accessors.js

Linting file: lib/node_modules/@stdlib/stats/base/dists/chisquare/mgf/lib/factory.js

Linting file: lib/node_modules/@stdlib/blas/ext/base/dapx/lib/dapx.native.js
make[1]: *** [/home/runner/work/stdlib/stdlib/tools/make/lib/lint/javascript/eslint.mk:255: eslint-files] Error 1
make[1]: Leaving directory '/home/runner/work/stdlib/stdlib'
make: *** [/home/runner/work/stdlib/stdlib/tools/make/lib/lint/javascript/Makefile:158: lint-javascript-files] Error 2

Pull Request Instructions

• Please use the following PR title format:
  "chore: fix JavaScript lint errors (issue #<ISSUE_NUMBER>)".
• Reference this issue in the "Related Issues" section of the PR body as "resolves #<ISSUE_NUMBER>".

[stdlib-bot]

👋 Important: PLEASE READ 👋

This issue has been labeled as a good first issue and is available for anyone to work on.

If this is your first time contributing to an open source project, some aspects of the development process may seem unusual, arcane, or some combination of both.

1. You cannot "claim" issues. People new to open source often want to "claim" or be assigned an issue before beginning work. The typical rationale is that people want to avoid wasted work in the event that someone else ends up working the issue. However, this practice is not effective in open source, as it often leads to "issue squatting", in which an individual asks to be assigned, is granted their request, and then never ends up working on the issue. Accordingly, you are encouraged to communicate your intent to address this issue, ideally by providing a rough outline as to how you plan to address the issue or asking clarifying questions, but, at the end of the day, we will take running code and rough consensus in order to move forward quickly.
2. We have a very high bar for contributions. We have very high standards for contributions and expect all contributions—whether new features, tests, or documentation—to be rigorous, thorough, and complete. Once a pull request is merged into stdlib, that contribution immediately becomes the collective responsibility of all maintainers of stdlib. When we merge code into stdlib, we are saying that we, the maintainers, commit to reviewing subsequent changes and making bugfixes to the code. Hence, in order to ensure future maintainability, this naturally leads to a higher standard of contribution.

Before working on this issue and opening a pull request, please read the project's contributing guidelines. These guidelines and the associated development guide provide important information, including links to stdlib's Code of Conduct, license policy, and steps for setting up your local development environment.

To reiterate, we strongly encourage you to refer to our contributing guides before beginning work on this issue. Failure to follow our guidelines significantly decreases the likelihood that you'll successfully contribute to stdlib and may result in automatic closure of a pull request without review.

Setting up your local development environment is a critical first step, as doing so ensures that automated development processes for linting, license verification, and unit testing can run prior to authoring commits and pushing changes. If you would prefer to avoid manual setup, we provide pre-configured development containers for use locally or in GitHub Codespaces.

We place a high value on consistency throughout the stdlib codebase. We encourage you to closely examine other packages in stdlib and attempt to emulate the practices and conventions found therein.

• If you are attempting to contribute a new package, sometimes the best approach is to simply copy the contents of an existing package and then modify the minimum amount necessary to implement the feature (e.g., changing descriptions, parameter names, and implementation).
• If you are contributing tests, find a package implementing a similar feature and emulate the tests of that package.
• If you are updating documentation, examine several similar packages and emulate the content, style, and prose of those packages.

In short, the more effort you put in to ensure that your contribution looks and feels like stdlib—including variables names, bracket spacing, line breaks, etc—the more likely that your contribution will be reviewed and ultimately accepted. We encourage you to closely study the codebase before beginning work on this issue.

✨ Thank you again for your interest in stdlib, and we look forward to reviewing your future contributions. ✨