stdlib-js / stdlib-js/stdlib

Fix JavaScript lint errors

Open
#8,586 3 comments 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/19619308578
- Type: JavaScript Linting
- Date: 2025-11-24 00:10:23 UTC

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

Linting file: lib/node_modules/@stdlib/_tools/eslint/rules/jsdoc-typedef-typos/lib/edit_distance.js

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

Linting file: lib/node_modules/@stdlib/ndarray/to-fancy/lib/defaults.js

Linting file: lib/node_modules/@stdlib/strided/napi/dmap2/lib/native.js

Linting file: lib/node_modules/@stdlib/_tools/markdown/img-svg-equation/lib/render.js

Linting file: lib/node_modules/@stdlib/math/base/special/minmaxabsf/lib/assign.js

Linting file: lib/node_modules/@stdlib/blas/ext/find-last-index/lib/main.js

Linting file: lib/node_modules/@stdlib/ml/incr/kmeans/lib/squared_correlation.js

Linting file: lib/node_modules/@stdlib/array/to-view-iterator/lib/index.js

Linting file: lib/node_modules/@stdlib/stats/strided/dcovarmtk/lib/dcovarmtk.js

Linting file: lib/node_modules/@stdlib/_tools/licenses/insert-header-file-list/lib/index.js

Oops! Something went wrong! :(

ESLint: 8.57.1

Error: ENOENT: no such file or directory, open '/home/runner/work/stdlib/stdlib/foo/bar.js'
Linting failed.

Linting file: lib/node_modules/@stdlib/dstructs/struct/lib/set_bigint.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 #".

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.