Fix JavaScript lint errors
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 95/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- javascript
- Domain
- tooling
Research direction
The error is in lib/node_modules/@stdlib/utils/every/examples/index.js at line 28: using new Array() is disallowed. Replace it with an array literal. Run the JavaScript lint workflow locally to verify the fix, then submit a pull request with the specified title and reference.
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/35800314574
- Type: JavaScript Linting
- Date: 2026-09-23 00:12:15 UTC
Error Details
make[1]: Entering directory '/home/runner/work/stdlib/stdlib'
Linting file: lib/node_modules/@stdlib/constants/float64/exponent-bias/examples/index.js
Linting file: lib/node_modules/@stdlib/utils/every/examples/index.js
/home/runner/work/stdlib/stdlib/lib/node_modules/@stdlib/utils/every/examples/index.js
28:7 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/blas/base/wasm/sdot/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 #<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)
- 558
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 1/5 Under an hour Newbie friendliness 88/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
-
Fix C lint errors Open
Difficulty 1/5 Under an hour Newbie friendliness 85/100
All issues in stdlib-js/stdlib
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
palladius/rails8-app-on-gcp#145 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
dotenvx/dotenv-vscode#139 ·
-
test-change-proposal
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
web-platform-tests/interop#1455 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
corsairdev/corsair#1764 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100