aglinxinyuan opened a new pull request, #4430:
URL: https://github.com/apache/texera/pull/4430
## Summary
This PR simplifies the `frontend/` dependency graph by removing unused
direct dependencies, dropping stale tooling packages, and keeping only the
runtime and type packages that are actually required by the current Angular
workspace.
## What changes were proposed in this PR?
- Removed unused direct runtime dependencies:
- `@loaders.gl/core`
- `@luma.gl/core`
- `@stoplight/json-ref-resolver`
- `backbone`
- `edit-distance`
- `es6-weak-map`
- `ng2-pdf-viewer`
- `ngx-image-viewer`
- `popper.js`
- `ts-proto`
- `vscode-ws-jsonrpc`
- Removed stale tooling dependencies:
- `@nrwl/cli`
- `@nrwl/nx-cloud`
- `nz-tslint-rules`
- `babel-plugin-dynamic-import-node`
- `ts-node`
- Kept `monaco-languageclient`, Angular devkit/schematics packages, and
other peer-driven dependencies that are still required by the current
workspace/tooling setup
- Kept `@types/lodash-es` and `@types/plotly.js-basic-dist-min` after
verifying they are required for TypeScript compilation
- Added `@bufbuild/protobuf` explicitly as a direct dependency because
checked-in generated protobuf TypeScript files import `@bufbuild/protobuf/wire`
at build time
- Regenerated `frontend/yarn.lock`
Several packages in `frontend/package.json` were no longer referenced by
application code, Angular config, Karma config, custom webpack config, or local
scripts. Some were only being retained accidentally through transitive installs.
This cleanup makes the dependency graph more intentional by:
- removing dead direct dependencies
- removing obsolete tooling leftovers
- making real compile/runtime dependencies explicit
### Any related issues, documentation, discussions?
Closes #4429
### How was this PR tested?
- `yarn.cmd install`
- `yarn.cmd build`
- `yarn.cmd test --watch=false`
Build and tests both pass.
### Was this PR authored or co-authored using generative AI tooling?
Generated-by: Codex
--
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]
