starred/devtools-detector

Fork 0

mirror of https://github.com/AEPKILL/devtools-detector.git synced 2026-04-26 23:15:48 +03:00

[GH-ISSUE #46] Disable console clearing #27

New issue

Closed

opened 2026-03-01 14:33:58 +03:00 by kerem · 11 comments

kerem commented

2026-03-01 14:33:58 +03:00

Owner

Originally created by @Valar353 on GitHub (Aug 16, 2022).
Original GitHub issue: https://github.com/AEPKILL/devtools-detector/issues/46

Hey! Is it possible to disable console clearing?

Originally created by @Valar353 on GitHub (Aug 16, 2022). Original GitHub issue: https://github.com/AEPKILL/devtools-detector/issues/46 Hey! Is it possible to disable console clearing?

kerem

2026-03-01 14:33:58 +03:00

closed this issue
added the
question
label

kerem commented

2026-03-01 14:33:58 +03:00

Author

Owner

@RVFET commented on GitHub (Aug 16, 2022):

You can overwrite console.clear() method, however it'll be still possible to use Browser's built-in "Clear console" button.

@RVFET commented on GitHub (Aug 16, 2022): You can overwrite ```console.clear()``` method, however it'll be still possible to use Browser's built-in "Clear console" button.

kerem commented

2026-03-01 14:33:58 +03:00

Author

Owner

@AEPKILL commented on GitHub (Aug 18, 2022):

If clear is disabled, a lot of information for detection will appear in the console (every detection loop)
If you want the your debugging information not to cleared, you can turn off the detection in the development environment

E.g.:

// __DEV__ may be injected by webpack or other bundle tools
if (!__DEV__) {  devtoolsDetector.launch() }

@AEPKILL commented on GitHub (Aug 18, 2022): If clear is disabled, a lot of information for detection will appear in the console (every detection loop) If you want the your debugging information not to cleared, you can turn off the detection in the development environment E.g.: ```ts // __DEV__ may be injected by webpack or other bundle tools if (!__DEV__) { devtoolsDetector.launch() } ```

kerem commented

2026-03-01 14:33:58 +03:00

Author

Owner

@Valar353 commented on GitHub (Aug 22, 2022):

Got it, thanks for the reply. However, the library clears the console before I call the launch method, is there any way to get around this?

@Valar353 commented on GitHub (Aug 22, 2022): Got it, thanks for the reply. However, the library clears the console before I call the `launch` method, is there any way to get around this?

kerem commented

2026-03-01 14:33:59 +03:00

Author

Owner

@AEPKILL commented on GitHub (Sep 7, 2022):

I just tried it won't clear the console before call the launch method

@AEPKILL commented on GitHub (Sep 7, 2022): I just tried it won't clear the console before call the `launch` method

kerem commented

2026-03-01 14:33:59 +03:00

Author

Owner

@jdempcy commented on GitHub (Sep 30, 2022):

I am using a package which uses devtoolsDetector (@d-i-t-a/reader) and so I do not have control over devtoolsDetector.launch() nor do I see that anywhere in the reader code. Is there another way to configure devtools-detector not to clear the console?

@jdempcy commented on GitHub (Sep 30, 2022): I am using a package which uses devtoolsDetector (@d-i-t-a/reader) and so I do not have control over devtoolsDetector.launch() nor do I see that anywhere in the reader code. Is there another way to configure devtools-detector not to clear the console?

kerem commented

2026-03-01 14:33:59 +03:00

Author

Owner

@AEPKILL commented on GitHub (Oct 29, 2022):

I am using a package which uses devtoolsDetector (@d-i-t-a/reader) and so I do not have control over devtoolsDetector.launch() nor do I see that anywhere in the reader code. Is there another way to configure devtools-detector not to clear the console?

you can rewrite devtoolsDetector.launch method before import @d-i-t-a/reader

e.g.


devtoolsDetector.launch = () => void

const reader = require("@d-i-t-a/reader")

@AEPKILL commented on GitHub (Oct 29, 2022): > I am using a package which uses devtoolsDetector (@d-i-t-a/reader) and so I do not have control over devtoolsDetector.launch() nor do I see that anywhere in the reader code. Is there another way to configure devtools-detector not to clear the console? you can rewrite `devtoolsDetector.launch` method before import `@d-i-t-a/reader` e.g. ```ts devtoolsDetector.launch = () => void const reader = require("@d-i-t-a/reader") ```

kerem commented

2026-03-01 14:33:59 +03:00

Author

Owner

@jdempcy commented on GitHub (Nov 18, 2022):

This disables other functionality used by the module for its content protection which requires detecting when the dev tools are open. What I really need to do is disable the console clearing. I actually found a way to do this by just pointing console.clear to an empty function, ilke you did with the launch method. In the index.html for the whole React app I simply add a script like so:

<!-- Disable console.clear() for debugging purposes -->
<script type="text/javascript">console.clear = () => {};</script>

Thanks for the great tool! And for the good idea of overriding the method like that :)

@jdempcy commented on GitHub (Nov 18, 2022): This disables other functionality used by the module for its content protection which requires detecting when the dev tools are open. What I really need to do is disable the console clearing. I actually found a way to do this by just pointing console.clear to an empty function, ilke you did with the launch method. In the index.html for the whole React app I simply add a script like so: ```  <script type="text/javascript">console.clear = () => {};</script> ``` Thanks for the great tool! And for the good idea of overriding the method like that :)

kerem commented

2026-03-01 14:33:59 +03:00

Author

Owner

@jdempcy commented on GitHub (Nov 18, 2022):

Hey! Is it possible to disable console clearing?

@Valar353 You can do this by overriding console.clear().

@jdempcy commented on GitHub (Nov 18, 2022): > Hey! Is it possible to disable console clearing? @Valar353 You can do this by overriding console.clear().

kerem commented

2026-03-01 14:33:59 +03:00

Author

Owner

@jdempcy commented on GitHub (Nov 18, 2022):

@AEPKILL this question can be closed as there is a suitable workaround (imo)

@jdempcy commented on GitHub (Nov 18, 2022): @AEPKILL this question can be closed as there is a suitable workaround (imo)

kerem commented

2026-03-01 14:33:59 +03:00

Author

Owner

@jdempcy commented on GitHub (Nov 18, 2022):

Note that pointing to void did not work for me and I actually had to override to an empty function with () => {}.

@jdempcy commented on GitHub (Nov 18, 2022): Note that pointing to void did not work for me and I actually had to override to an empty function with () => {}.

kerem commented

2026-03-01 14:33:59 +03:00

Author

Owner

@jfaylon commented on GitHub (Jul 21, 2025):

I'm trying to override the console.clear but to no avail. Is there a way to disable the logs for this module instead of clearing as this affects globally?

@jfaylon commented on GitHub (Jul 21, 2025): I'm trying to override the console.clear but to no avail. Is there a way to disable the logs for this module instead of clearing as this affects globally?

kerem referenced this issue

2026-03-01 17:27:32 +03:00

[GH-ISSUE #27] Chrome issue #95