Commit activity
Last 12 weeks · 0 commits
Community health
3 of 6 standards met
57
✓README✓License✓Contributing○Code of Conduct○Issue Template○PR Template
Recent PRs & issues
Quiet · 1 in progress · Last activity 3y ago
See all on GitHub →
Super minor, but actually defaults to : https://github.com/developit/optimize-plugin/blob/7e43e02621742c4fb6bb8272d6bd56e62ba588a4/src/index.js#L45-L49
webpack@5.10.0 optimize-plugin@1.0.0 node: v15.2.0
In the ReadMe, there's the following line: In order to migrate to optimize-plugin, you'll need to move your babel configuration into a or file ...optimize-plugin only uses your babel configuration when generating _modern_ bundles. However, both and are set to : https://github.com/developit/optimize-plugin/blob/aefb895750e217be250230f9c0cb78afc00aa4fe/src/worker.js#L59-L61 This should stop any config files from being loaded, AFAIK. Am I misunderstanding something, or are the docs outdated perhaps?
Recent fixes
Well this was a fun one to find... Notably, it'll incorrectly convert into . Funky name, to be fair.
Issue came from testing out in . While CLI's setup is pretty niche, this issue can arise if is initialized but then removed from the Webpack config (like if a user strips it out using their ). This seems to lock up the Webpack build, never allowing it to complete. Moving pool creation to when Webpack actually installs the plugin seems to correct the issue.
Hi. This plugin working with module federation?
Structured data for AI agents
Repository: developit/optimize-plugin. Description: Optimized Webpack Bundling for Everyone. Intro ⤵️ Stars: 651, Forks: 13. Primary language: JavaScript. Languages: JavaScript (100%). License: Apache-2.0. Homepage: https://youtu.be/cLxNdLK--yI?t=662 Topics: modern-javascript, webpack, webpack-plugin. Latest release: 1.3.0 (4y ago). Open PRs: 1, open issues: 4. Last activity: 3y ago. Community health: 57%. Top contributors: developit, dangreen, rschristian, JoviDeCroock, DreierF, alireza-mh.