kunwp1 commented on PR #3795:
URL: https://github.com/apache/texera/pull/3795#issuecomment-3367325365
For this library, our frontend code doesn’t use it directly. Instead,
Angular and Nx rely on it indirectly to ensure TypeScript compiles into
browser-compatible code. In this case, is there a protocol or systematic way to
check for regressions? Do you think running CI tests (frontend unit tests) is
sufficient?
```
➜ gui git:(main) yarn why @babel/helpers
├─ @babel/core@npm:7.22.9
│ └─ @babel/helpers@npm:7.28.4 (via npm:^7.22.6)
│
├─ @babel/core@npm:7.23.2
│ └─ @babel/helpers@npm:7.28.4 (via npm:^7.23.2)
│
└─ @babel/core@npm:7.25.8
└─ @babel/helpers@npm:7.28.4 (via npm:^7.25.7)
➜ gui git:(main) yarn why @babel/core
├─ @angular-devkit/build-angular@npm:16.2.12
│ └─ @babel/core@npm:7.22.9 (via npm:7.22.9)
│
├─ @angular-devkit/build-angular@npm:16.2.16
│ └─ @babel/core@npm:7.22.9 (via npm:7.22.9)
│
├─ @angular-devkit/build-angular@npm:16.2.12 [125e9]
│ └─ @babel/core@npm:7.22.9 (via npm:7.22.9)
│
├─ @angular-devkit/build-angular@npm:16.2.16 [e8b71]
│ └─ @babel/core@npm:7.22.9 (via npm:7.22.9)
│
├─ @angular/compiler-cli@npm:16.2.12
│ └─ @babel/core@npm:7.23.2 (via npm:7.23.2)
│
├─ @angular/compiler-cli@npm:16.2.12 [125e9]
│ └─ @babel/core@npm:7.23.2 (via npm:7.23.2)
│
├─ @angular/localize@npm:16.2.12
│ └─ @babel/core@npm:7.23.2 (via npm:7.23.2)
│
├─ @angular/localize@npm:16.2.12 [125e9]
│ └─ @babel/core@npm:7.23.2 (via npm:7.23.2)
│
├─ @nx/js@npm:20.0.3
│ └─ @babel/core@npm:7.25.8 (via npm:^7.23.2)
│
├─ @nx/js@npm:20.0.3 [51472]
│ └─ @babel/core@npm:7.25.8 (via npm:^7.23.2)
│
├─ @nx/webpack@npm:20.0.3
│ └─ @babel/core@npm:7.25.8 (via npm:^7.23.2)
│
└─ istanbul-lib-instrument@npm:5.2.1
└─ @babel/core@npm:7.25.8 (via npm:^7.12.3)
```
--
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]
