Skip to content

Fix JavaScript lint errors #16332

Closed

Description

@stdlib-bot

JavaScript Linting Failures

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

Workflow Details

Error Details

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

Linting file: lib/node_modules/@stdlib/math/base/special/versinf/examples/index.js
versinf(2.8651) = 1.9620
versinf(3.2060) = 1.9979
versinf(1.7314) = 1.1599
versinf(1.4569) = 0.8864
versinf(6.2564) = 0.0004
versinf(1.4178) = 0.8476
versinf(4.7927) = 0.9198
versinf(3.0327) = 1.9941
versinf(3.6382) = 1.8792
versinf(0.2197) = 0.0240
versinf(3.8068) = 1.7868
versinf(3.6892) = 1.8538
versinf(5.6106) = 0.2178
versinf(4.8063) = 0.9062
versinf(6.0792) = 0.0207
versinf(5.5795) = 0.2375
versinf(4.8387) = 0.8740
versinf(4.5628) = 1.1490
versinf(2.2369) = 1.6180
versinf(2.0598) = 1.4698
versinf(5.2775) = 0.4645
versinf(2.5482) = 1.8290
versinf(2.8747) = 1.9646
versinf(1.5742) = 1.0034
versinf(0.6699) = 0.2161
versinf(3.2755) = 1.9910
versinf(4.7880) = 0.9245
versinf(2.8862) = 1.9676
versinf(3.0535) = 1.9961
versinf(4.4042) = 1.3034
versinf(5.8648) = 0.0862
versinf(6.2591) = 0.0003
versinf(2.6798) = 1.8953
versinf(3.5445) = 1.9199
versinf(3.8076) = 1.7863
versinf(4.9165) = 0.7973
versinf(0.8232) = 0.3201
versinf(3.2441) = 1.9948
versinf(5.8009) = 0.1141
versinf(0.2028) = 0.0205
versinf(0.4891) = 0.1172
versinf(5.5575) = 0.2519
versinf(1.0183) = 0.4752
versinf(0.8531) = 0.3423
versinf(3.9401) = 1.6978
versinf(3.5695) = 1.9098
versinf(0.3912) = 0.0755
versinf(3.6077) = 1.8933
versinf(1.7199) = 1.1486
versinf(6.0728) = 0.0220
versinf(3.4472) = 1.9537
versinf(0.8775) = 0.3610
versinf(3.0312) = 1.9939
versinf(0.4035) = 0.0803
versinf(2.9773) = 1.9865
versinf(4.7496) = 0.9628
versinf(5.9539) = 0.0537
versinf(4.6541) = 1.0583
versinf(1.6961) = 1.1249
versinf(1.8887) = 1.3126
versinf(3.0904) = 1.9987
versinf(5.5022) = 0.2898
versinf(0.8239) = 0.3207
versinf(4.2406) = 1.4545
versinf(5.0606) = 0.6588
versinf(2.8068) = 1.9445
versinf(2.5000) = 1.8012
versinf(5.8724) = 0.0832
versinf(5.5758) = 0.2400
versinf(2.0336) = 1.4464
versinf(2.7811) = 1.9357
versinf(2.7297) = 1.9163
versinf(3.9809) = 1.6680
versinf(1.3992) = 0.8293
versinf(2.6919) = 1.9006
versinf(3.0298) = 1.9938
versinf(2.1326) = 1.5327
versinf(4.0598) = 1.6073
versinf(4.0919) = 1.5814
versinf(0.4670) = 0.1071
versinf(1.7927) = 1.2201
versinf(5.4346) = 0.3389
versinf(1.9239) = 1.3458
versinf(6.0629) = 0.0242
versinf(5.2604) = 0.4790
versinf(3.2041) = 1.9980
versinf(4.9321) = 0.7821
versinf(0.3706) = 0.0679
versinf(6.1406) = 0.0102
versinf(5.4359) = 0.3380
versinf(4.2337) = 1.4606
versinf(4.9155) = 0.7983
versinf(5.4987) = 0.2922
versinf(0.2114) = 0.0223
versinf(0.2999) = 0.0446
versinf(2.6769) = 1.8939
versinf(4.3162) = 1.3859
versinf(4.5244) = 1.1868
versinf(3.3822) = 1.9712
versinf(3.9666) = 1.6785

Linting file: lib/node_modules/@stdlib/blas/ext/base/sdsapxsum/examples/index.js

Linting file: lib/node_modules/@stdlib/blas/base/wasm/csrot/examples/module.js

Linting file: lib/node_modules/@stdlib/constants/float64/pinf/examples/index.js

/home/runner/work/stdlib/stdlib/lib/node_modules/@stdlib/constants/float64/pinf/examples/index.js
22:1  error  Displayed return value is `Number.POSITIVE_INFINITY`, but expected `Infinity` instead  stdlib/doctest

✖ 1 problem (1 error, 0 warnings)
1 error and 0 warnings potentially fixable with the `--fix` option.

Linting failed.
make[1]: *** [/home/runner/work/stdlib/stdlib/tools/make/lib/lint/javascript/eslint.mk:261: 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
make[1]: Entering directory '/home/runner/work/stdlib/stdlib'

Linting file: lib/node_modules/@stdlib/_tools/github/get/test/fixtures/response.js

Linting file: lib/node_modules/@stdlib/blas/base/dscal/test/test.ndarray.native.js

Linting file: lib/node_modules/@stdlib/blas/ext/base/gsumors/test/test.main.js

Linting file: lib/node_modules/@stdlib/assert/is-float32ndarray-like/test/test.js

Linting file: lib/node_modules/@stdlib/stats/base/ndarray/svariancech/test/test.native.js

Linting file: lib/node_modules/@stdlib/ndarray/numel-dimension/test/test.js

Linting file: lib/node_modules/@stdlib/random/erlang/test/test.factory.js

Linting file: lib/node_modules/@stdlib/assert/is-gzip-buffer/test/test.js

/home/runner/work/stdlib/stdlib/lib/node_modules/@stdlib/assert/is-gzip-buffer/test/test.js
52:87  error  Unused eslint-disable directive (no problems were reported from 'no-buffer-constructor')
80:21  error  Unused eslint-disable directive (no problems were reported from 'no-buffer-constructor')
81:21  error  Unused eslint-disable directive (no problems were reported from 'no-buffer-constructor')

✖ 3 problems (3 errors, 0 warnings)
3 errors and 0 warnings potentially fixable with the `--fix` option.

Linting failed.

Linting file: lib/node_modules/@stdlib/math/strided/special/sabs/test/test.sabs.native.js

Linting file: lib/node_modules/@stdlib/blas/ext/base/snansumkbn2/test/test.ndarray.native.js

Linting file: lib/node_modules/@stdlib/utils/async/until/test/test.js

Linting file: lib/node_modules/@stdlib/stats/base/dists/chisquare/kurtosis/test/test.js

Linting file: lib/node_modules/@stdlib/blas/ext/base/ndarray/dsum/test/test.js

Linting file: lib/node_modules/@stdlib/random/chisquare/test/test.assign.js

Linting file: lib/node_modules/@stdlib/math/base/special/acoshf/test/test.js
make[1]: *** [/home/runner/work/stdlib/stdlib/tools/make/lib/lint/javascript/eslint.mk:261: 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>".

Activity

  1. stdlib-bot commented on Oct 28, 2026

    @stdlib-bot
    ContributorAuthor

    👋 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. ✨

  2. added a commit that references this issue on Oct 30, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Good First IssueA good first issue for new contributors!

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions