Skip to content

[2.x] chore: update JS tooling (flarum-webpack-config ^3.1.0, webpack-cli ^7.2.3, typescript ^5.9.3) - #19

Merged
imorland merged 1 commit into
2.xfrom
im/flarum-js-tooling
Oct 23, 2026
Merged

imorland merged 1 commit into
2.xfrom
im/flarum-js-tooling

Conversation

@imorland

Copy link
Copy Markdown
Member

Changes proposed in this pull request:
Brings the JS tooling in line with flarum/framework and @flarum/cli:

  • flarum-webpack-config: ^3.0.7 → ^3.1.0
  • webpack-cli: ^4.9.1 → ^7.2.3
  • typescript: ^4.5.4 → ^5.9.3

typescript is declared directly so tsc stays linked under package managers that only link the binaries of direct dependencies. webpack-cli 7 needs Node 20.9 or later. yarn.lock is updated without a full regeneration.

No release needed: the rebuilt bundle is not expected to change.

Reviewers should focus on:
No source changes. yarn check-typings, yarn format-check and yarn build pass. check-typings now runs on TypeScript 5.9 instead of 4.9. regenerate is deduplicated to 1.5.0, as jest-config's README recommends, so Babel does not end up with two copies. Also removes the stale js/package-lock.json: the frontend workflow already installs with yarn (js_package_manager: yarn), and yarn.lock is the lockfile it uses.

Confirmed

  • Frontend changes: tested on a local Flarum installation.
  • Frontend changes: tests are green (run yarn test in js/).
  • Frontend changes: tests have been added, or are not appropriate here.
  • Core developer confirmed locally this works as intended.
  • The description above is written by me and describes what this pull request actually does.

@imorland
imorland marked this pull request as ready for review October 23, 2026 10:41
@imorland
imorland merged commit f790e68 into 2.x Oct 23, 2026
22 checks passed
@imorland
imorland deleted the im/flarum-js-tooling branch October 23, 2026 10:44
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