stdlib-js / stdlib-js/stdlib

Fix JavaScript lint errors

Offen Anfängerfreundlich
#12,359 1 Kommentar 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen
Good First Issue
Vorherrschende Sprache
JavaScript
Sterne
6k
Forks
1.3k
Ø Merge
1 T. 3 Std.
Gemergte PRs (30 T.)
611

Beschreibung

## 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/26668990373
- Type: JavaScript Linting
- Date: 2026-05-30 00:34:49 UTC

### Error Details
```
make[1]: Entering directory '/home/runner/work/stdlib/stdlib'

Linting file: lib/node_modules/@stdlib/console/examples/index.js

Linting file: lib/node_modules/@stdlib/stats/base/dists/geometric/skewness/examples/index.js
p: 0.9505, skew(X;p): 4.7168
p: 0.5205, skew(X;p): 2.1366
p: 0.4122, skew(X;p): 2.0710
p: 0.0896, skew(X;p): 2.0022
p: 0.6988, skew(X;p): 2.3710
p: 0.9170, skew(X;p): 3.7596
p: 0.6690, skew(X;p): 2.3134
p: 0.3413, skew(X;p): 2.0437
p: 0.6831, skew(X;p): 2.3393
p: 0.6507, skew(X;p): 2.2830

Linting file: lib/node_modules/@stdlib/math/base/tools/evalpoly-compile/examples/index.js

/home/runner/work/stdlib/stdlib/lib/node_modules/@stdlib/math/base/tools/evalpoly-compile/examples/index.js
23:18 error Last `require` statement in example files must be a relative path stdlib/require-last-path-relative

✖ 1 problem (1 error, 0 warnings)

Linting failed.

Linting file: lib/node_modules/@stdlib/number/uint16/base/sub/examples/index.js
33 - 1 = 32
32 - 49 = 65519
28 - 35 = 65529
15 - 31 = 65520
6 - 42 = 65500
4 - 28 = 65512
37 - 16 = 21
3 - 12 = 65527
39 - 9 = 30
26 - 16 = 10
20 - 13 = 7
25 - 27 = 65534
20 - 25 = 65531
23 - 39 = 65520
23 - 44 = 65515
44 - 42 = 2
40 - 45 = 65531
33 - 44 = 65525
48 - 29 = 19
16 - 46 = 65506
46 - 29 = 17
49 - 2 = 47
29 - 42 = 65523
8 - 47 = 65497
42 - 18 = 24
0 - 4 = 65532
7 - 29 = 65514
17 - 11 = 6
45 - 40 = 5
28 - 23 = 5
19 - 5 = 14
20 - 48 = 65508
33 - 6 = 27
42 - 34 = 8
11 - 50 = 65497
37 - 40 = 65533
29 - 29 = 0
21 - 50 = 65507
12 - 26 = 65522
8 - 1 = 7
25 - 9 = 16
21 - 47 = 65510
40 - 8 = 32
26 - 47 = 65515
11 - 22 = 65525
47 - 33 = 14
25 - 35 = 65526
12 - 3 = 9
12 - 35 = 65513
47 - 9 = 38
29 - 49 = 65516
45 - 8 = 37
32 - 25 = 7
41 - 16 = 25
17 - 39 = 65514
33 - 40 = 65529
40 - 37 = 3
34 - 43 = 65527
47 - 20 = 27
1 - 10 = 65527
1 - 35 = 65502
2 - 36 = 65502
25 - 43 = 65518
9 - 16 = 65529
17 - 14 = 3
3 - 12 = 65527
32 - 18 = 14
8 - 29 = 65515
47 - 30 = 17
43 - 42 = 1
28 - 30 = 65534
43 - 29 = 14
33 - 12 = 21
32 - 2 = 30
46 - 26 = 20
10 - 39 = 65507
3 - 48 = 65491
11 - 25 = 65522
11 - 47 = 65500
16 - 24 = 65528
5 - 31 = 65510
29 - 20 = 9
17 - 43 = 65510
20 - 31 = 65525
28 - 28 = 0
16 - 18 = 65534
19 - 15 = 4
6 - 27 = 65515
15 - 34 = 65517
12 - 43 = 65505
32 - 22 = 10
48 - 46 = 2
36 - 10 = 26
42 - 25 = 17
1 - 8 = 65529
15 - 41 = 65510
20 - 4 = 16
14 - 17 = 65533
36 - 16 = 20
46 - 21 = 25

Linting file: lib/node_modules/@stdlib/random/iter/triangular/examples/index.js

Linting file: lib/node_modules/@stdlib/streams/node/from-circular-array/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 #)".
- Reference this issue in the "Related Issues" section of the PR body as "resolves #".

Beitragsleitfaden

Beitragsleitfaden öffnen

Rechercherichtung

Start with lib/node_modules/@stdlib/math/base/tools/evalpoly-compile/examples/index.js at line 23 and inspect the require statements in that example. Run the JavaScript lint target shown in the failure, and consider the work done when the lint workflow completes without errors.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Bewertung

Tech-Stack
eslint, javascript
Bereich
tooling
Issue-Typ
Bug
Schwierigkeit
1/5
Geschätzter Aufwand
Unter einer Stunde
Aktivitätsstatus
Ruhig
Klarheit
Klar beschrieben
Anfängerfreundlichkeit
78/100

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.