mirror of
https://github.com/ntop/ntopng.git
synced 2026-07-10 00:14:24 +00:00
|
|
||
|---|---|---|
| .. | ||
| vue_components | ||
| AddClickhouseColumns.md | ||
| cpp_flows_sorting.md | ||
| README.add_new_pref.md | ||
| README.add_preference.md | ||
| README.Add_startup_param.md | ||
| README.alerts.md | ||
| README.dashboard_timeseries.md | ||
| README.flow_state.md | ||
| README.GUI.frontend.md | ||
| README.GUI.ntopng_utility_js.md | ||
| README.GUI.quickstart.md | ||
| README.GUI.utilization.md | ||
| README.hash_entries_lifecycle.md | ||
| README.hr.md | ||
| README.OIDC.md | ||
| README.passkey.md | ||
| README.pref_input_box.md | ||
| README.recording.md | ||
| README.report_dashboard.md | ||
| README.tags.md | ||
| README.timeseries.md | ||
| README.UI.architecture.md | ||
| README.update_frontend_CVE.md | ||
How to update a CVE on the frontend
If a new CVE arises for the frontend, the file to change is package.json. In this file there is the definition for all the frontend dependencies.
For example to update vite version, first find the package to update, then change the version. Below an example
"vite": "^6.3.5", -> "vite": "^6.4.3",
Then, to verify that everything works, in ntopng/:
# remove installed dependencies
rm -rf node_modules/
# reinstall dependencies with new package version
npm install
# build the dist for the frontend
npm run build
Then, after having reinstalled dependencies and rebuilt the dist, navigate to the ntopng UI, check that there are no errors in console that were not present before.
For example, if package X was to be updated, check that in all pages affecting package X, everything works as before.