Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Angular 15+16 compile gets stuck at "70% sealing finish module graph ESLintWebpackPlugin_1" #223

Closed
Usama129 opened this issue May 24, 2023 · 4 comments

Comments

@Usama129
Copy link

Usama129 commented May 24, 2023

I'm using eslint-webpack-plugin 4.0.1 with Angular 16.0.2, and webpack-dev-server 4.15.0 and node v18.16.0.
My compile process (with webpack-dev-server) succeeds initially and goes to 100%. When I change/edit a .ts or .scss file, the re-compile gets stuck at "70% sealing finish module graph ESLintWebpackPlugin_1".

plugin webpack config as follows:

new ESLintPlugin({
extensions: ["ts"],
failOnWarning: false,
failOnError: true,
emitError: true,
cache: true,
cacheStrategy: "content",
lintDirtyModulesOnly: true,
fix: true
})

Also encountered on Angular 15 with eslint-webpack-plugin 3.2.0 and webpack-dev-server 4.11.1 with node 16.x

Things we've tried:
cache properties - nope, not related to cache
fix:true disabled - not related
changing order of plugins - nope
update to node 20 - nope

@StraightOuttaCrompton
Copy link

I'm having the same issue. Initially succeeds but fails when a file is changed.

Plugin config can be found at https://github.com/ProtonMail/WebClients/blob/main/packages/pack/webpack/plugins.js#L42

Tried similar fixes as above, and the only fix is to not include the plugin at all.

None of my colleagues are affected by this, but I am running the older macbook pro with intel chip.

Any advice would be appreciated 🙏

@StraightOuttaCrompton
Copy link

StraightOuttaCrompton commented Dec 15, 2023

Seems to be causing an issue with storybook too storybookjs/storybook#18051

@dikaso
Copy link

dikaso commented Apr 10, 2024

Set threads to true, it helps.

@ricardogobbosouza
Copy link
Collaborator

I can't reproduce.
If the problem persists, provide a repository

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

No branches or pull requests

4 participants