Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Fix JavaScript lint errors

Aperta Adatta ai principianti
  • Qualcosa non va?
#12,195 3 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

@nathanaelmbale ci sta già lavorando.

Dal 26/5/2026.

  • #12205 di @ArrushiTripathi2429 — chiusa senza merge
  • #12304 di @nathanaelmbale — aperta

Valutazione

Difficoltà
1/5
Tempo stimato
Meno di un'ora
Idoneità per principianti
78/100
Tipo di issue
Bug
Chiarezza
Specificata chiaramente
Stato di attività
Tranquilla
Stack tecnologico
javascript
Ambito
tooling

Direzione di ricerca

Inizia da lib/node_modules/@stdlib/ndarray/slice-to/test/test.js alle righe 637-641 e 669-673, dove il workflow di lint JavaScript segnala dieci errori stdlib/line-closing-bracket-spacing. Esegui il workflow di lint JavaScript o ESLint per questo file, quindi conferma che il target lint-javascript-files venga completato senza errori.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

Good First Issue

JavaScript Linting Failures

Linting failures were detected in the automated JavaScript lint workflow run.

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

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

Linting file: lib/node_modules/@stdlib/random/array/chi/test/test.js

Linting file: lib/node_modules/@stdlib/math/base/special/absf/test/test.native.js

Linting file: lib/node_modules/@stdlib/stats/base/dists/laplace/logcdf/test/test.logcdf.js

Linting file: lib/node_modules/@stdlib/error/reviver/test/test.ctors.js

Linting file: lib/node_modules/@stdlib/blas/base/wasm/saxpy/test/test.module.ndarray.js

Linting file: lib/node_modules/@stdlib/dstructs/named-typed-tuple/test/test.copy_within.js

Linting file: lib/node_modules/@stdlib/blas/ext/base/dsort2hp/test/test.dsort2hp.js

Linting file: lib/node_modules/@stdlib/ndarray/slice-to/test/test.js

/home/runner/work/stdlib/stdlib/lib/node_modules/@stdlib/ndarray/slice-to/test/test.js
637:3  error  No spaces allowed between a closing parenthesis or bracket and a nested object or array expression at the beginning of a line  stdlib/line-closing-bracket-spacing
638:3  error  No spaces allowed between a closing parenthesis or bracket and a nested object or array expression at the beginning of a line  stdlib/line-closing-bracket-spacing
639:3  error  No spaces allowed between a closing parenthesis or bracket and a nested object or array expression at the beginning of a line  stdlib/line-closing-bracket-spacing
640:3  error  No spaces allowed between a closing parenthesis or bracket and a nested object or array expression at the beginning of a line  stdlib/line-closing-bracket-spacing
641:3  error  No spaces allowed between a closing parenthesis or bracket and a nested object or array expression at the beginning of a line  stdlib/line-closing-bracket-spacing
669:3  error  No spaces allowed between a closing parenthesis or bracket and a nested object or array expression at the beginning of a line  stdlib/line-closing-bracket-spacing
670:3  error  No spaces allowed between a closing parenthesis or bracket and a nested object or array expression at the beginning of a line  stdlib/line-closing-bracket-spacing
671:3  error  No spaces allowed between a closing parenthesis or bracket and a nested object or array expression at the beginning of a line  stdlib/line-closing-bracket-spacing
672:3  error  No spaces allowed between a closing parenthesis or bracket and a nested object or array expression at the beginning of a line  stdlib/line-closing-bracket-spacing
673:3  error  No spaces allowed between a closing parenthesis or bracket and a nested object or array expression at the beginning of a line  stdlib/line-closing-bracket-spacing

✖ 10 problems (10 errors, 0 warnings)
10 errors and 0 warnings potentially fixable with the `--fix` option.

Linting failed.

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

Linting file: lib/node_modules/@stdlib/stats/strided/distances/deuclidean/test/test.js

Linting file: lib/node_modules/@stdlib/array/float32/test/test.js

Linting file: lib/node_modules/@stdlib/blas/ext/base/sdsnansumpw/test/test.js

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

Linting file: lib/node_modules/@stdlib/_tools/eslint/rules/jsdoc-heading-style/test/fixtures/valid.js

Linting file: lib/node_modules/@stdlib/stats/strided/nanmean/test/test.ndarray.js

Linting file: lib/node_modules/@stdlib/stats/strided/smean/test/test.smean.native.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>".
Lingua principale
JavaScript
Stelle
6k
Fork
1.3k
Merge medio
1g 8h
PR unite (30g)
586

Preparare l'ambiente

Apri in Codespaces

Avvia il container di sviluppo del progetto nel browser, con il tuo account GitHub.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di stdlib-js/stdlib

Tutte le issue di stdlib-js/stdlib

Issue simili

Altre issue su JavaScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.