aglinxinyuan opened a new issue, #6161:
URL: https://github.com/apache/texera/issues/6161

   ### Task Summary
   
   The frontend `analyze` npm script — `ng build --configuration=production 
--stats-json && webpack-bundle-analyzer dist/stats.json` — is a manual, 
developer-only bundle-inspection helper. It and its `webpack-bundle-analyzer` 
devDependency are worth dropping:
   
   - **Not wired into anything.** No build, CI, container, or test path invokes 
`yarn analyze`; the `--stats-json` flag is used by this one script only.
   - **No programmatic use.** `webpack-bundle-analyzer` / 
`BundleAnalyzerPlugin` is not imported anywhere — the frontend is a stock 
Angular CLI project with no custom webpack config, so nothing keeps the 
dependency alive.
   - **Dev-only.** It is a devDependency and not part of the binary 
distribution, so there is no `LICENSE-binary` entry to maintain.
   - **Less to maintain** — one fewer devDependency and its transitive tree 
(`sirv`, `gzip-size`, `commander`, `mrmime`, `duplexer`, `totalist`, `ws`).
   
   Split out of #4997 per review 
(https://github.com/apache/texera/pull/4997#discussion_r3524565737), where the 
removal was flagged as unrelated to the monaco-languageclient v10 upgrade.
   
   ### Scope
   
   | File | Change |
   | --- | --- |
   | `frontend/package.json` | Drop the `"analyze"` script and the 
`"webpack-bundle-analyzer": "4.5.0"` devDependency |
   | `frontend/yarn.lock` | Regenerate — removes `webpack-bundle-analyzer` and 
its exclusive transitive deps; deps shared with other packages stay |
   | `frontend/README.md` | Drop the stale `Bundle analyzer → yarn analyze` row 
from the "Common commands" table |
   
   Addressed by #6156.
   
   ### Task Type
   
   - [x] Refactor / Cleanup
   - [ ] DevOps / Deployment / CI
   - [ ] Testing / QA
   - [ ] Documentation
   - [ ] Performance
   - [ ] Other
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to