Skip to content

Conversation

yicheny
Copy link

@yicheny yicheny commented Dec 6, 2022

Currently, webpack5 caching is not working

If the cache was in effect, it would generate files with a '.pack' suffix, like :

rs5-has-cache

And now, the generated result looks like this:

rs5-no-cache

The reason is that 'compiler.close()' is not called

webpack will generate the cache in 'compiler.close()'

Run 'npm run build' to verify the effect

has a huge impact on compilation speed in a project

@melloware
Copy link

This should absolutely be accepted.

@Crypto555top
Copy link

Thanks you're the best friend ever! Happy New Year #bitcoinluis Crypto. 1/8/2023

@Crypto555top
Copy link

God is there to help us thank goodness #bitcoinluis #bitcoin

@hunter2009
Copy link

Can anyone handle this issue?
According to webpack doc, it's necessary to close the comliper after running it:
Don't forget to close the compiler, so that low-priority work (like persistent caching) have the opportunity to complete.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants