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/18513403697
• Type: JavaScript Linting
• Date: 2025-10-15 00:12:38 UTC

Error Details

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

Linting file: lib/node_modules/@stdlib/utils/type-max/examples/index.js

/home/runner/work/stdlib/stdlib/lib/node_modules/@stdlib/utils/type-max/examples/index.js
23:1  error  Displayed return value is `+infinity`, but expected `Infinity` instead  stdlib/doctest
23:1  error  Displayed return value is `+infinity`, but expected `Infinity` instead  stdlib/doctest
23:1  error  Displayed return value is `+infinity`, but expected `Infinity` instead  stdlib/doctest

✖ 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/base/special/maxabs/examples/index.js
maxabs(278.8091,134.8502) = 278.8091
maxabs(321.2425,241.7093) = 321.2425
maxabs(-327.0301,250.8507) = 327.0301
maxabs(6.3924,202.2474) = 202.2474
maxabs(-399.5325,-263.5553) = 399.5325
maxabs(-387.6935,-426.5094) = 426.5094
maxabs(-386.8013,260.0695) = 386.8013
maxabs(-95.1869,-432.4407) = 432.4407
maxabs(-281.7466,35.9698) = 281.7466
maxabs(203.6774,-170.2051) = 203.6774
maxabs(79.4535,53.7884) = 79.4535
maxabs(30.3077,-71.2226) = 71.2226
maxabs(463.9588,483.3649) = 483.3649
maxabs(432.7314,-143.5639) = 432.7314
maxabs(-388.6895,478.6573) = 478.6573
maxabs(297.3758,-372.8962) = 372.8962
maxabs(240.8243,-261.1760) = 261.1760
maxabs(411.3117,291.4273) = 411.3117
maxabs(479.5974,-339.0813) = 479.5974
maxabs(-171.2122,-373.5866) = 373.5866
maxabs(-368.1373,173.7546) = 368.1373
maxabs(370.2737,-54.0560) = 370.2737
maxabs(-62.3109,81.7741) = 81.7741
maxabs(32.6172,-60.8287) = 60.8287
maxabs(-171.0473,9.2185) = 171.0473
maxabs(-81.8569,-262.1037) = 262.1037
maxabs(77.8265,-37.6256) = 77.8265
maxabs(146.1186,126.8080) = 146.1186
maxabs(-218.1664,357.9614) = 357.9614
maxabs(-135.2114,131.2972) = 135.2114
maxabs(-208.2013,-340.6960) = 340.6960
maxabs(-107.8483,432.3363) = 432.3363
maxabs(-239.0216,383.1447) = 383.1447
maxabs(263.1398,-498.5851) = 498.5851
maxabs(290.9626,-40.2737) = 290.9626
maxabs(251.8819,-253.1690) = 253.1690
maxabs(177.8867,-89.7202) = 177.8867
maxabs(-356.7936,-84.7458) = 356.7936
maxabs(-327.7593,253.5406) = 327.7593
maxabs(-270.3000,458.9918) = 458.9918
maxabs(-440.1566,-381.9604) = 440.1566
maxabs(161.1396,301.1760) = 301.1760
maxabs(-385.0577,-71.3753) = 385.0577
maxabs(425.9579,-281.7767) = 425.9579
maxabs(90.3540,-396.9340) = 396.9340
maxabs(111.2514,-490.8292) = 490.8292
maxabs(-91.3129,95.5024) = 95.5024
maxabs(-241.6026,-105.8497) = 241.6026
maxabs(-65.3049,442.1110) = 442.1110
maxabs(-178.0413,277.4504) = 277.4504
maxabs(223.4456,-79.6631) = 223.4456
maxabs(-268.3019,-443.8957) = 443.8957
maxabs(397.1898,18.2599) = 397.1898
maxabs(364.2834,485.7053) = 485.7053
maxabs(313.5132,-340.7996) = 340.7996
maxabs(-345.7952,-118.5640) = 345.7952
maxabs(171.8085,-271.5601) = 271.5601
maxabs(260.9949,-419.4961) = 419.4961
maxabs(22.1936,1.7628) = 22.1936
maxabs(337.3391,161.3725) = 337.3391
maxabs(74.5811,-330.2008) = 330.2008
maxabs(-68.0044,-126.8463) = 126.8463
maxabs(-31.3602,-427.1614) = 427.1614
maxabs(391.3479,-287.6787) = 391.3479
maxabs(-103.9427,-126.7537) = 126.7537
maxabs(165.6302,259.4195) = 259.4195
maxabs(164.1088,-487.5898) = 487.5898
maxabs(-393.5648,365.5050) = 393.5648
maxabs(251.9797,-56.9969) = 251.9797
maxabs(-131.0203,198.7822) = 198.7822
maxabs(-121.7778,71.4966) = 121.7778
maxabs(-81.9174,-162.3997) = 162.3997
maxabs(388.8629,204.3462) = 388.8629
maxabs(-457.6410,-346.7802) = 457.6410
maxabs(-130.8752,-87.3192) = 130.8752
maxabs(388.1293,193.9555) = 388.1293
maxabs(-102.5415,-180.0520) = 180.0520
maxabs(-263.3543,0.3917) = 263.3543
maxabs(-225.5329,-29.6647) = 225.5329
maxabs(-425.7954,-21.0796) = 425.7954
maxabs(-337.8319,355.5601) = 355.5601
maxabs(151.5179,99.2547) = 151.5179
maxabs(402.2975,-442.6773) = 442.6773
maxabs(-438.5388,-191.5285) = 438.5388
maxabs(107.7145,20.1529) = 107.7145
maxabs(383.8075,373.3500) = 383.8075
maxabs(-131.3405,-57.2882) = 131.3405
maxabs(-99.3564,-300.2867) = 300.2867
maxabs(-345.4873,473.5536) = 473.5536
maxabs(477.5933,388.9275) = 477.5933
maxabs(85.3510,367.6675) = 367.6675
maxabs(-263.1129,-50.6281) = 263.1129
maxabs(434.2061,445.0665) = 445.0665
maxabs(437.0726,468.5138) = 468.5138
maxabs(299.0674,-126.9556) = 299.0674
maxabs(444.1903,-491.0051) = 491.0051
maxabs(284.4178,-43.1211) = 284.4178
maxabs(342.5110,-21.0347) = 342.5110
maxabs(124.6285,92.7633) = 124.6285
maxabs(-204.5449,11.7130) = 204.5449

Linting file: lib/node_modules/@stdlib/string/base/pascalcase/examples/index.js

Linting file: lib/node_modules/@stdlib/ndarray/base/prepend-singleton-dimensions/examples/index.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>".

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