Description
Debug logging left in component code runs in the production bundle and writes to every visitor's browser console.
1. src/components/SistentNavigation/intra-page.js:68
const anchors = document.querySelectorAll(".main-content > a");
console.log(anchors);
IntraPage is rendered by SistentLayout, so this logs a NodeList on every Sistent documentation page load.
2. src/sections/Learn-Layer5/Course-Overview/index.js:165-169
{console.log(
"lenght of the service mesh array: ",
availableServiceMeshes.length,
)}
{console.log("array: ", availableServiceMeshes)}
Two logs embedded directly in JSX, so they fire on every render of the course overview page. (Note the lenght typo in the log text.) Because console.log returns undefined, these expressions render nothing — they are purely debug output.
3. src/sections/Home/So-Special-Section/index.js:124-125
Commented-out console.log calls that can be deleted as part of the same cleanup.
Expected Behavior
No debug logging in the production bundle. The three sites above should be removed. Genuine error reporting in catch blocks (e.g. CatalogGrid.js:29, Features-Col/index.js:80) is intentional and should stay, though console.error would be more appropriate than console.log for those.
Please note: src/sections/Projects/Sistent/getting-started/usage/index.js:95 also contains console.log('Form submitted:', formData), but that line lives inside a documentation code-sample string shown to readers as example code. It is not a bug and should be left alone.
Screenshots
N/A — open any Sistent component docs page with devtools and observe the logged NodeList.
Environment:
- Host OS: any
- Browser: any
Description
Debug logging left in component code runs in the production bundle and writes to every visitor's browser console.
1.
src/components/SistentNavigation/intra-page.js:68IntraPageis rendered bySistentLayout, so this logs aNodeListon every Sistent documentation page load.2.
src/sections/Learn-Layer5/Course-Overview/index.js:165-169Two logs embedded directly in JSX, so they fire on every render of the course overview page. (Note the
lenghttypo in the log text.) Becauseconsole.logreturnsundefined, these expressions render nothing — they are purely debug output.3.
src/sections/Home/So-Special-Section/index.js:124-125Commented-out
console.logcalls that can be deleted as part of the same cleanup.Expected Behavior
No debug logging in the production bundle. The three sites above should be removed. Genuine error reporting in
catchblocks (e.g.CatalogGrid.js:29,Features-Col/index.js:80) is intentional and should stay, thoughconsole.errorwould be more appropriate thanconsole.logfor those.Please note:
src/sections/Projects/Sistent/getting-started/usage/index.js:95also containsconsole.log('Form submitted:', formData), but that line lives inside a documentation code-sample string shown to readers as example code. It is not a bug and should be left alone.Screenshots
N/A — open any Sistent component docs page with devtools and observe the logged
NodeList.Environment: