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/23075521096
• Type: JavaScript Linting
• Date: 2026-03-14 03:36:54 UTC

Error Details

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

Linting file: lib/node_modules/@stdlib/math/base/special/rcbrt/examples/index.js
rcbrt(79) = 0.2331
rcbrt(17) = 0.3889
rcbrt(81) = 0.2311
rcbrt(97) = 0.2176
rcbrt(6) = 0.5503
rcbrt(60) = 0.2554
rcbrt(56) = 0.2614
rcbrt(19) = 0.3748
rcbrt(28) = 0.3293
rcbrt(94) = 0.2199
rcbrt(16) = 0.3969
rcbrt(100) = 0.2154
rcbrt(64) = 0.2500
rcbrt(95) = 0.2192
rcbrt(55) = 0.2630
rcbrt(80) = 0.2321
rcbrt(54) = 0.2646
rcbrt(73) = 0.2393
rcbrt(5) = 0.5848
rcbrt(24) = 0.3467
rcbrt(90) = 0.2231
rcbrt(55) = 0.2630
rcbrt(69) = 0.2438
rcbrt(53) = 0.2662
rcbrt(0) = infinity
rcbrt(81) = 0.2311
rcbrt(63) = 0.2513
rcbrt(65) = 0.2487
rcbrt(37) = 0.3001
rcbrt(28) = 0.3293
rcbrt(58) = 0.2583
rcbrt(49) = 0.2733
rcbrt(95) = 0.2192
rcbrt(39) = 0.2949
rcbrt(46) = 0.2791
rcbrt(18) = 0.3816
rcbrt(79) = 0.2331
rcbrt(50) = 0.2714
rcbrt(75) = 0.2371
rcbrt(84) = 0.2283
rcbrt(13) = 0.4253
rcbrt(62) = 0.2527
rcbrt(73) = 0.2393
rcbrt(31) = 0.3183
rcbrt(17) = 0.3889
rcbrt(20) = 0.3684
rcbrt(42) = 0.2877
rcbrt(45) = 0.2811
rcbrt(68) = 0.2450
rcbrt(59) = 0.2569
rcbrt(55) = 0.2630
rcbrt(77) = 0.2351
rcbrt(82) = 0.2302
rcbrt(92) = 0.2215
rcbrt(74) = 0.2382
rcbrt(33) = 0.3118
rcbrt(40) = 0.2924
rcbrt(16) = 0.3969
rcbrt(67) = 0.2462
rcbrt(20) = 0.3684
rcbrt(34) = 0.3087
rcbrt(63) = 0.2513
rcbrt(12) = 0.4368
rcbrt(62) = 0.2527
rcbrt(61) = 0.2540
rcbrt(16) = 0.3969
rcbrt(10) = 0.4642
rcbrt(29) = 0.3255
rcbrt(6) = 0.5503
rcbrt(86) = 0.2266
rcbrt(94) = 0.2199
rcbrt(70) = 0.2426
rcbrt(8) = 0.5000
rcbrt(50) = 0.2714
rcbrt(36) = 0.3029
rcbrt(56) = 0.2614
rcbrt(79) = 0.2331
rcbrt(8) = 0.5000
rcbrt(19) = 0.3748
rcbrt(77) = 0.2351
rcbrt(21) = 0.3625
rcbrt(79) = 0.2331
rcbrt(66) = 0.2474
rcbrt(23) = 0.3516
rcbrt(87) = 0.2257
rcbrt(91) = 0.2223
rcbrt(44) = 0.2833
rcbrt(53) = 0.2662
rcbrt(63) = 0.2513
rcbrt(66) = 0.2474
rcbrt(6) = 0.5503
rcbrt(23) = 0.3516
rcbrt(88) = 0.2248
rcbrt(18) = 0.3816
rcbrt(70) = 0.2426
rcbrt(28) = 0.3293
rcbrt(52) = 0.2679
rcbrt(94) = 0.2199
rcbrt(10) = 0.4642
rcbrt(14) = 0.4149

Linting file: lib/node_modules/@stdlib/constants/time/milliseconds-in-second/examples/index.js

Linting file: lib/node_modules/@stdlib/math/base/special/asecd/examples/index.js
asecd(-9.7749) = 95.8718
asecd(5.2103) = 78.9347
asecd(3.8634) = 74.9987
asecd(-3.0816) = 108.9357
asecd(9.8891) = 84.1963
asecd(-3.6035) = 106.1114
asecd(9.8633) = 84.1810
asecd(6.0102) = 80.4224
asecd(-6.1772) = 99.3163
asecd(-7.4712) = 97.6919
asecd(8.3821) = 83.1482
asecd(-9.5529) = 96.0087
asecd(-2.8158) = 110.8023
asecd(1.5340) = 49.3159
asecd(-4.1144) = 104.0666
asecd(-2.2208) = 116.7616
asecd(-7.0671) = 98.1347
asecd(-5.6541) = 100.1872
asecd(9.5008) = 83.9582
asecd(-0.6878) = nan
asecd(-7.3092) = 97.8635
asecd(-1.7803) = 124.1739
asecd(0.3816) = nan
asecd(-6.9835) = 98.2327
asecd(1.9904) = 59.8403
asecd(3.2386) = 72.0145
asecd(-1.1831) = 147.6989
asecd(-9.9804) = 95.7505
asecd(-3.8415) = 105.0887
asecd(-5.1558) = 101.1838
asecd(-1.7165) = 125.6315
asecd(3.7416) = 74.4983
asecd(-0.9667) = nan
asecd(8.0589) = 82.8720
asecd(3.8541) = 74.9618
asecd(6.1275) = 80.6073
asecd(-6.7146) = 98.5649
asecd(8.8691) = 83.5261
asecd(7.3150) = 82.1428
asecd(6.7669) = 81.5018
asecd(-9.6329) = 95.9586
asecd(4.6438) = 77.5646
asecd(5.7923) = 80.0585
asecd(8.9378) = 83.5761
asecd(2.3440) = 64.7468
asecd(5.8949) = 80.2332
asecd(6.2905) = 80.8529
asecd(-1.1849) = 147.5623
asecd(-4.6528) = 102.4112
asecd(1.8174) = 56.6172
asecd(-9.7999) = 95.8568
asecd(-0.6083) = nan
asecd(-9.2769) = 96.1882
asecd(4.3186) = 76.6112
asecd(8.3260) = 83.1018
asecd(6.1761) = 80.6820
asecd(6.3242) = 80.9020
asecd(-3.6036) = 106.1111
asecd(2.7426) = 68.6160
asecd(-4.9739) = 101.5982
asecd(8.9592) = 83.5915
asecd(6.3212) = 80.8978
asecd(0.4961) = nan
asecd(3.3627) = 72.6998
asecd(-8.7327) = 96.5755
asecd(9.4676) = 83.9369
asecd(8.8050) = 83.4788
asecd(7.9543) = 82.7778
asecd(-6.6625) = 98.6323
asecd(3.5025) = 73.4108
asecd(3.2547) = 72.1065
asecd(-8.9160) = 96.4397
asecd(3.8459) = 74.9289
asecd(-3.3216) = 107.5214
asecd(-4.3683) = 103.2337
asecd(-7.4280) = 97.7370
asecd(0.3093) = nan
asecd(-5.0559) = 101.4076
asecd(-4.2559) = 103.5897
asecd(-4.1655) = 103.8905
asecd(-6.1863) = 99.3025
asecd(7.2359) = 82.0563
asecd(3.7459) = 74.5164
asecd(6.3459) = 80.9335
asecd(-7.5755) = 97.5854
asecd(-6.3225) = 99.1005
asecd(-1.8106) = 123.5257
asecd(-5.2079) = 101.0705
asecd(4.5609) = 77.3348
asecd(8.6626) = 83.3710
asecd(3.1657) = 71.5856
asecd(-2.2737) = 116.0916
asecd(-2.0973) = 118.4771
asecd(-2.5832) = 112.7750
asecd(0.2877) = nan
asecd(-0.2385) = nan
asecd(6.2095) = 80.7325
asecd(-1.0034) = 175.2911
asecd(-3.8269) = 105.1476
asecd(7.8542) = 82.6852

Linting file: lib/node_modules/@stdlib/blas/tools/swap-factory/examples/index.js

Linting file: lib/node_modules/@stdlib/math/base/special/acscf/examples/index.js
acscf(4.6328) = 0.2176
acscf(3.4017) = 0.2984
acscf(4.5926) = 0.2195
acscf(2.1322) = 0.4882
acscf(1.3092) = 0.8692
acscf(2.3214) = 0.4454
acscf(1.9005) = 0.5541
acscf(1.5295) = 0.7126
acscf(5.0635) = 0.1988
acscf(3.5501) = 0.2855
acscf(3.8917) = 0.2599
acscf(1.9639) = 0.5343
acscf(1.9717) = 0.5319
acscf(2.6430) = 0.3880
acscf(1.9306) = 0.5445
acscf(2.4902) = 0.4132
acscf(2.2362) = 0.4636
acscf(1.8959) = 0.5556
acscf(4.0415) = 0.2500
acscf(4.3550) = 0.2317
acscf(1.7284) = 0.6170
acscf(3.5064) = 0.2892
acscf(1.4224) = 0.7797
acscf(4.1584) = 0.2429
acscf(3.3308) = 0.3049
acscf(1.6614) = 0.6459
acscf(5.0084) = 0.2010
acscf(3.5486) = 0.2857
acscf(1.2704) = 0.9062
acscf(4.2690) = 0.2364
acscf(4.1646) = 0.2425
acscf(4.7340) = 0.2128
acscf(4.7892) = 0.2104
acscf(1.8550) = 0.5693
acscf(1.6833) = 0.6361
acscf(2.5160) = 0.4087
acscf(1.3875) = 0.8048
acscf(2.3681) = 0.4360
acscf(1.4309) = 0.7738
acscf(1.8452) = 0.5728
acscf(4.4111) = 0.2287
acscf(2.9036) = 0.3516
acscf(2.4633) = 0.4180
acscf(4.2824) = 0.2357
acscf(1.7562) = 0.6058
acscf(4.1297) = 0.2446
acscf(4.8994) = 0.2056
acscf(3.3733) = 0.3010
acscf(1.9517) = 0.5379
acscf(3.7726) = 0.2683
acscf(3.7835) = 0.2675
acscf(4.1078) = 0.2459
acscf(3.8846) = 0.2604
acscf(3.5816) = 0.2830
acscf(4.0868) = 0.2472
acscf(4.9147) = 0.2049
acscf(4.7825) = 0.2106
acscf(2.5379) = 0.4050
acscf(3.7843) = 0.2674
acscf(4.4017) = 0.2292
acscf(4.4550) = 0.2264
acscf(4.6967) = 0.2146
acscf(2.8109) = 0.3637
acscf(3.3952) = 0.2990
acscf(2.9660) = 0.3439
acscf(1.8050) = 0.5872
acscf(3.0485) = 0.3342
acscf(4.3983) = 0.2294
acscf(3.3538) = 0.3028
acscf(4.2911) = 0.2352
acscf(2.3409) = 0.4414
acscf(3.5761) = 0.2834
acscf(3.2857) = 0.3093
acscf(4.6811) = 0.2153
acscf(4.5776) = 0.2202
acscf(2.2839) = 0.4532
acscf(2.5980) = 0.3951
acscf(2.8356) = 0.3604
acscf(3.2763) = 0.3102
acscf(4.2056) = 0.2401
acscf(4.6024) = 0.2190
acscf(3.0423) = 0.3349
acscf(5.0877) = 0.1978
acscf(1.4215) = 0.7803
acscf(1.4726) = 0.7465
acscf(3.4480) = 0.2943
acscf(5.0918) = 0.1977
acscf(3.1016) = 0.3283
acscf(3.8632) = 0.2618
acscf(4.8923) = 0.2059
acscf(4.2826) = 0.2357
acscf(3.9048) = 0.2590
acscf(3.1418) = 0.3239
acscf(2.6973) = 0.3798
acscf(3.8001) = 0.2663
acscf(4.9687) = 0.2026
acscf(2.3256) = 0.4445
acscf(4.3595) = 0.2314
acscf(1.3208) = 0.8589
acscf(2.9817) = 0.3420

Linting file: lib/node_modules/@stdlib/utils/regexp-from-string/examples/index.js

/home/runner/work/stdlib/stdlib/lib/node_modules/@stdlib/utils/regexp-from-string/examples/index.js
1:1  error  Displayed return value is `/\\\//ig`, but expected `/\\\//gi` 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

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