JS-0002 · Avoid using `console` in code that runs on browser

Avoid using console in code that runs on browser JS-0002

Bug risk

Major

2 months ago — 2 years old

Avoid using console in code that runs on the browser

 12  const navigate = useNavigate();
 13  useEffect(() => {
 14    if (user) {
 15      console.log("remember me", user); 16      navigate("/home");
 17    }
 18  }, []);

Avoid using console in code that runs on the browser

src/views/home/POS.tsx

215            })}
216          >
217            {carts.map((cart, index) => {
218              console.log(cart.id);219              return (
220                <option key={index} value={cart.id}>
221                  Cart {index + 1} created at{" "}

Avoid using console in code that runs on the browser

src/views/home/CheckoutTable.tsx

178                                  );
179                                }}
180                                onBlur={(e) => {
181                                  console.log("blur");182                                }}
183                                type="number"
184                              />

Avoid using console in code that runs on the browser

src/views/home/Checkout.tsx

 88      });
 89  };
 90  const handleSubmitCart = () => {
 91    console.log("submit"); 92  };
 93
 94  const calculateTotal = (total, discount) => {

Avoid using console in code that runs on the browser

src/redux/slices/productSlice.ts

 68        ).toFixed(2);
 69        product.data.tax = parseInt(newTax);
 70      }
 71      console.log(product.data); 72      const response = await axios.patch(
 73        `${PRODUCTS_URL}/${data.id}` + ".json",
 74        product.data

Description

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)

Huthaifa-Dev / project

Bad Practice

Recommended