Skip to content

Move to ESLint 10 and @microbit/eslint-config 0.2.1 - #147

Merged
microbit-matt-hillsdon merged 1 commit into
mainfrom
eslint-10
Sep 1, 2026
Merged

Move to ESLint 10 and @microbit/eslint-config 0.2.1#147
microbit-matt-hillsdon merged 1 commit into
mainfrom
eslint-10

Conversation

@microbit-matt-hillsdon

Copy link
Copy Markdown
Contributor

eslint-react reports eleven things in the demo app that the old plugin did not. Three are real:

Serial and UART both cap their log at 200 lines with slice(-200), so every append past the cap shifts each remaining line down an index. Keying by index there means React rewrites the text of reused nodes instead of matching lines to nodes. Harmless for plain text, wrong the moment a row holds focus or state, so both now carry a line id.

PinsTab built a Set or Map on every render to seed state it only uses once. Lazy initialisers.

The rest are the LED grids and the flash timings table, where the index really is the identity: a fixed 5x5 matrix and an append-only list. Disabled at the four sites with a reason.

npm cannot resolve this bump in one step. The lockfile pins the old shared config with its eslint ^9.7 peer and npm tries to reconcile that rather than replace it, failing with a circular ERESOLVE. Uninstall eslint and @microbit/eslint-config first, then install the new pair.

eslint-react reports eleven things in the demo app that the old plugin
did not. Three are real:

Serial and UART both cap their log at 200 lines with slice(-200), so
every append past the cap shifts each remaining line down an index.
Keying by index there means React rewrites the text of reused nodes
instead of matching lines to nodes. Harmless for plain text, wrong the
moment a row holds focus or state, so both now carry a line id.

PinsTab built a Set or Map on every render to seed state it only uses
once. Lazy initialisers.

The rest are the LED grids and the flash timings table, where the index
really is the identity: a fixed 5x5 matrix and an append-only list.
Disabled at the four sites with a reason.

npm cannot resolve this bump in one step. The lockfile pins the old
shared config with its eslint ^9.7 peer and npm tries to reconcile that
rather than replace it, failing with a circular ERESOLVE. Uninstall
eslint and @microbit/eslint-config first, then install the new pair.
@microbit-matt-hillsdon
microbit-matt-hillsdon merged commit e29c78e into main Sep 1, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant