Fix JavaScript lint errors
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 88/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- javascript
- Domain
- tooling
Research direction
Start with lib/node_modules/@stdlib/_tools/makie/plugins/makie-view-complexity/lib/main.js at line 92, where the JavaScript lint workflow reports the only error. Inspect the surrounding code and run the JavaScript lint command or workflow shown in tools/make/lib/lint/javascript/Makefile. Done means the reported no-new-array error is resolved and linting passes.
Written by the indexing model from the issue text.
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/35670342293
- Type: JavaScript Linting
- Date: 2026-09-22 00:16:02 UTC
Error Details
make[1]: Entering directory '/home/runner/work/stdlib/stdlib'
Linting file: lib/node_modules/@stdlib/blas/ext/base/dnancount/lib/ndarray.native.js
Linting file: lib/node_modules/@stdlib/random/frechet/lib/factory.js
Linting file: lib/node_modules/@stdlib/assert/is-complex128/lib/main.js
Linting file: lib/node_modules/@stdlib/random/array/minstd/lib/validate.js
Linting file: lib/node_modules/@stdlib/array/base/bifurcate-entries-by/lib/index.js
Linting file: lib/node_modules/@stdlib/ndarray/base/any/lib/4d_blocked_accessors.js
Linting file: lib/node_modules/@stdlib/stats/strided/dpcorr/lib/dpcorr.js
Linting file: lib/node_modules/@stdlib/array/falses/lib/main.js
Linting file: lib/node_modules/@stdlib/constants/float32/min-base10-exponent-subnormal/lib/index.js
Linting file: lib/node_modules/@stdlib/proxy/lib/index.js
Linting file: lib/node_modules/@stdlib/array/base/any/lib/main.js
Linting file: lib/node_modules/@stdlib/blas/ext/base/dtriu2tril/lib/ndarray.js
Linting file: lib/node_modules/@stdlib/math/base/special/hacoversin/lib/native.js
Linting file: lib/node_modules/@stdlib/stats/strided/dnanstdev/lib/index.js
Linting file: lib/node_modules/@stdlib/math/base/special/absgammalnf/lib/polyval_t2.js
Linting file: lib/node_modules/@stdlib/_tools/eslint/rules/no-builtin-big-int/lib/index.js
Linting file: lib/node_modules/@stdlib/slice/base/seq2slice/lib/re_end.js
Linting file: lib/node_modules/@stdlib/streams/node/empty/lib/factory.js
Linting file: lib/node_modules/@stdlib/math/base/assert/is-composite/lib/main.js
Linting file: lib/node_modules/@stdlib/assert/is-symbol/lib/polyfill.js
Linting file: lib/node_modules/@stdlib/blas/ext/base/saxpb/lib/ndarray.js
Linting file: lib/node_modules/@stdlib/regexp/utf16-unpaired-surrogate/lib/main.js
Linting file: lib/node_modules/@stdlib/stats/base/ndarray/meanpn/lib/main.js
Linting file: lib/node_modules/@stdlib/_tools/makie/plugins/makie-view-complexity/lib/main.js
/home/runner/work/stdlib/stdlib/lib/node_modules/@stdlib/_tools/makie/plugins/makie-view-complexity/lib/main.js
92:9 error Using the `new Array()` constructor is not allowed; use an array literal with push instead stdlib/no-new-array
✖ 1 problem (1 error, 0 warnings)
Linting failed.
Linting file: lib/node_modules/@stdlib/constants/time/hours-in-day/lib/index.js
Linting file: lib/node_modules/@stdlib/random/base/chisquare/lib/main.js
Linting file: lib/node_modules/@stdlib/_tools/licenses/insert-header/lib/main.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>".
- Dominant language
- JavaScript
- Stars
- 6k
- Forks
- 1.3k
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 551
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from stdlib-js/stdlib
-
Good First Issue
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
-
Good First Issue
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Good First Issue
Difficulty 1/5 Under an hour Newbie friendliness 88/100
-
Good First Issue
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
All issues in stdlib-js/stdlib
Similar issues
-
bot:ai-assisted component:compact-js status:untriaged
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
midnightntwrk/midnight-sdk#403 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 92/100
-
Difficulty 1/5 1-3 hours Newbie friendliness 86/100
DavidAnson/markdownlint-cli2#940 ·
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
githubnext/gh-aw-workshop#3692 ·
-
agent/guide documentation hive/hosted-available-lke648397-260827-5n31
Difficulty 2/5 1-3 hours Newbie friendliness 90/100