console in code that runs on browser JS-0002241 setLocalStorage("user", result.payload);
242 console.log(result.payload);
243 authenticate(response, () => {
244 console.log(response);245 toast(`Welcome back ${username}!`, {
246 type: "success",
247 bodyClassName: "toastify-body",239 .then((result) => {
240 console.log(result);
241 setLocalStorage("user", result.payload);
242 console.log(result.payload);243 authenticate(response, () => {
244 console.log(response);
245 toast(`Welcome back ${username}!`, {237 await importSPKI(MATRIX_RSA_PUBLIC_KEY, "RS256"),
238 )
239 .then((result) => {
240 console.log(result);241 setLocalStorage("user", result.payload);
242 console.log(result.payload);
243 authenticate(response, () => {231 username,
232 })
233 .then(async (response) => {
234 console.log(response);235 jwtVerify(
236 response.data.token,
237 await importSPKI(MATRIX_RSA_PUBLIC_KEY, "RS256"),It is considered a best practice to avoid the use of any console methods in JavaScript code that will run on the browser.
NOTE: If your repository contains a server side project, you can add "nodejs" to the environment property of analyzer meta in .deepsource.toml.
This will prevent this issue from getting raised.
Documentation for the analyzer meta can be found here.
Alternatively, you can silence this issue for your repository as shown here.
If a specific console call is meant to stay for other reasons, you can add a skipcq comment to that line.
This will inform other developers about the reason behind the log's presence, and prevent DeepSource from flagging it.
Usually, console methods are only used for debugging, and can leak internal info to the client.
Removing the console call will fix this issue.
Bad Practice
if (!secure(data)) {
console.log("data is not secure", data) // `data` is visible to the client
}
console.table(tableObj)
Recommended
if (!secure(data)) {
// alter the DOM to inform the user that `data` is insecure.
}
console.table(tableObj) // skipcq: JS-0002 Easter egg. Users are meant to see this.