Skip to content

Feature/nxt 18691: Added improvements for webpack - #399

Open
daniel-stoian-lgp wants to merge 4 commits into
developfrom
feature/NXT-18691
Open

Feature/nxt 18691: Added improvements for webpack#399
daniel-stoian-lgp wants to merge 4 commits into
developfrom
feature/NXT-18691

Conversation

@daniel-stoian-lgp

@daniel-stoian-lgp daniel-stoian-lgp commented Aug 21, 2026

Copy link
Copy Markdown
Contributor

Checklist

  • I have read and understand the contribution guide
  • A CHANGELOG entry is included
  • I have run automated testing and it is passed
  • Documentation was added or is not needed
  • This is an API breaking change

Issue Resolved / Feature Added

Two webpack-path performance fixes, found by per-hook profiling of enact pack -p against limestone/samples/qa-a11y.

  1. Run ESLint overlapped instead of blocking the build
    Profiling showed eslint-webpack-plugin's processAssets wait was the single largest atomic chunk of the whole build (~5.5 s on a cold qa-a11y build)
    The cause is structural: the library only invokes its linter at compilation.hooks.finishModules, i.e. after webpack has already built the entire module graph. There is almost nothing left to overlap with, so the lint cost lands squarely in the critical path.

This replaces it with config/eslint-overlap-plugin.js, which spawns ESLint as a real child process at compiler.hooks.run / watchRun (before any module is built) and only awaits it at processAssets ,the same stage the original used, so plugin ordering relative to ILibPlugin etc. is unchanged. By the time processAssets is reached the child has usually already finished, making the await close to free.

Resolution

Additional Considerations

Links

nxt 18691

Comments

@daniel-stoian-lgp daniel-stoian-lgp changed the title Feature/nxt 18691 Feature/nxt 18691: Added improvements for webpack Aug 21, 2026
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