You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Description
We shouldn't use outdated/deprecated packages, because it's slowing down the build and could be a potential vulnerability in the future, so we need to clean up npm warns from the build.
2024-11-06T21:18:30.1987032Z npm install
2024-11-06T21:18:46.8454614Z npm warn deprecated @npmcli/[email protected]: This functionality has been moved to @npmcli/fs
2024-11-06T21:18:47.6173714Z npm warn deprecated @babel/[email protected]: This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-private-property-in-object instead.
2024-11-06T21:18:49.0137530Z npm warn deprecated @npmcli/[email protected]: This functionality has been moved to @npmcli/fs
2024-11-06T21:18:54.3468251Z npm warn deprecated [email protected]: You can find the new Popper v2 at @popperjs/core, this package is dedicated to the legacy v1
2024-11-06T21:18:54.3816285Z npm warn deprecated [email protected]: no longer supported
2024-11-06T21:19:04.5971075Z npm warn deprecated [email protected]: core-js@<3.23.3 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Some versions have web compatibility issues. Please, upgrade your dependencies to the actual version of core-js.
2024-11-06T21:19:04.6091194Z npm warn deprecated [email protected]: core-js@<3.23.3 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Some versions have web compatibility issues. Please, upgrade your dependencies to the actual version of core-js.
2024-11-06T21:19:20.5635974Z
2024-11-06T21:19:20.5638076Z > @kyma-project/[email protected] postinstall
2024-11-06T21:19:20.5638618Z > cd backend && npm install
2024-11-06T21:19:20.5639031Z
2024-11-06T21:19:26.3205850Z npm warn deprecated [email protected]: Please see https://github.com/lydell/urix#deprecated
2024-11-06T21:19:26.4226849Z npm warn deprecated [email protected]: See https://github.com/lydell/source-map-url#deprecated
2024-11-06T21:19:26.5690267Z npm warn deprecated [email protected]: https://github.com/lydell/resolve-url#deprecated
2024-11-06T21:19:26.8289330Z npm warn deprecated [email protected]: See https://github.com/lydell/source-map-resolve#deprecated
2024-11-06T21:19:31.5646178Z
2024-11-06T21:19:31.5648125Z added 910 packages, and audited 911 packages in 11s
2024-11-06T21:19:31.5648472Z
2024-11-06T21:19:31.5648803Z 72 packages are looking for funding
2024-11-06T21:19:31.5649284Z run `npm fund` for details
2024-11-06T21:19:31.5958157Z
2024-11-06T21:19:31.5958882Z 12 vulnerabilities (2 low, 3 moderate, 7 high)
Reasons
We shouldn't use outdated/deprecated packages, because it's slowing down the build and could be a potential vulnerability in the future.
Description
We shouldn't use outdated/deprecated packages, because it's slowing down the build and could be a potential vulnerability in the future, so we need to clean up
npm warns
from the build.Reasons
We shouldn't use outdated/deprecated packages, because it's slowing down the build and could be a potential vulnerability in the future.
Attachments
The text was updated successfully, but these errors were encountered: