stdlib-js / stdlib-js/stdlib

Fix JavaScript lint errors

Open
#6,383 1 comment 0 reactions 0 assignees View on GitHub
Good First Issue
Dominant language
JavaScript
Stars
6k
Forks
1.3k
Avg merge
1d 3h
Merged PRs (30d)
611

Description

## 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/14072437970
- Type: JavaScript Linting
- Date: 2025-03-26 00:08:34 UTC

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

Linting file: lib/node_modules/@stdlib/stats/base/dists/pareto-type1/pdf/lib/factory.js

Linting file: lib/node_modules/@stdlib/plot/components/svg/axis/lib/props/tick-pos/get.js

Linting file: lib/node_modules/@stdlib/stats/base/dists/t/ctor/lib/main.js

Linting file: lib/node_modules/@stdlib/_tools/pkgs/namespace-readmes/lib/index.js

Linting file: lib/node_modules/@stdlib/array/base/mskfilter/lib/assign.js

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

Linting file: lib/node_modules/@stdlib/blas/base/gscal/lib/ndarray.js

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

Linting file: lib/node_modules/@stdlib/stats/base/dists/f/mean/lib/index.js

Linting file: lib/node_modules/@stdlib/datasets/sotu/lib/get_file.js

/home/runner/work/stdlib/stdlib/lib/node_modules/@stdlib/datasets/sotu/lib/get_file.js
51:58 warning Unknown word: "zalgo" @cspell/spellchecker

✖ 1 problem (0 errors, 1 warning)

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

Linting file: lib/node_modules/@stdlib/lapack/base/zrot/lib/ndarray.js

Linting file: lib/node_modules/@stdlib/plot/base/ctor/lib/main.js

/home/runner/work/stdlib/stdlib/lib/node_modules/@stdlib/plot/base/ctor/lib/main.js
248:32 warning Unexpected 'todo' comment: 'TODO: uuid' no-warning-comments
801:1 warning File has too many lines (399). Maximum allowed is 300 max-lines
1026:1 error Encountered an error while running code: `invalid format: %H:%M`.Did you mean to include a `// throws ` annotation instead of `// returns `? stdlib/jsdoc-doctest

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

Linting failed.

Linting file: lib/node_modules/@stdlib/plot/components/svg/marks/lib/validate.js

Linting file: lib/node_modules/@stdlib/stats/base/dists/lognormal/logpdf/lib/main.js

Linting file: lib/node_modules/@stdlib/number/lib/index.js

Linting file: lib/node_modules/@stdlib/stats/base/dists/t/logcdf/lib/factory.js

Linting file: lib/node_modules/@stdlib/stats/base/dists/beta/entropy/lib/native.js

Linting file: lib/node_modules/@stdlib/ndarray/base/nullary/lib/7d.js

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

Linting file: lib/node_modules/@stdlib/ndarray/index/lib/cache.js

Linting file: lib/node_modules/@stdlib/stats/base/dists/betaprime/skewness/lib/native.js

Linting file: lib/node_modules/@stdlib/random/base/hypergeometric/lib/factory.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 #)".
- Reference this issue in the "Related Issues" section of the PR body as "resolves #".

Contributor guide

Open the contributing guide

Research direction

Start by rerunning the JavaScript lint workflow or the relevant make target, then inspect the reported locations in lib/node_modules/@stdlib/plot/base/ctor/lib/main.js and lib/node_modules/@stdlib/datasets/sotu/lib/get_file.js. Check the lint output around main.js line 1026 and the listed warnings. Done means the JavaScript lint run completes without errors or warnings.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
tooling
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.