[GH-ISSUE #51] Remix logs unusable from 500-item JSON object logged by performance.checker.ts #30

Closed
opened 2026-03-01 14:33:59 +03:00 by kerem · 4 comments
Owner

Originally created by @jdempcy on GitHub (Nov 18, 2022).
Original GitHub issue: https://github.com/AEPKILL/devtools-detector/issues/51

In Remix apps the console log of the repeated 500-item JSON object logged by performance.checker.ts is put into the server logs, rendering them unusable (since console.clear() does nothing there) filling up over 10,000 lines in every page load.

    '480': '480',
    '481': '481',
    '482': '482',
    '483': '483',
    '484': '484',
    '485': '485',
    '486': '486',
    '487': '487',
    '488': '488',
    '489': '489',
    '490': '490',
    '491': '491',
    '492': '492',
    '493': '493',
    '494': '494',
    '495': '495',
    '496': '496',
    '497': '497',
    '498': '498',
    '499': '499'

etc, looping over and over.

I have not been able to fix this by overriding devtoolsDetector.launch() as advised in another issue (of console clearing). That solution did not work. Is there a way to add an option to devtools-detector to disable this performance.checker.ts logging?

Originally created by @jdempcy on GitHub (Nov 18, 2022). Original GitHub issue: https://github.com/AEPKILL/devtools-detector/issues/51 In Remix apps the console log of the repeated 500-item JSON object logged by performance.checker.ts is put into the server logs, rendering them unusable (since console.clear() does nothing there) filling up over 10,000 lines in every page load. ``` '480': '480', '481': '481', '482': '482', '483': '483', '484': '484', '485': '485', '486': '486', '487': '487', '488': '488', '489': '489', '490': '490', '491': '491', '492': '492', '493': '493', '494': '494', '495': '495', '496': '496', '497': '497', '498': '498', '499': '499' ``` etc, looping over and over. I have not been able to fix this by overriding devtoolsDetector.launch() as advised in another issue (of console clearing). That solution did not work. Is there a way to add an option to devtools-detector to disable this performance.checker.ts logging?
kerem 2026-03-01 14:33:59 +03:00
  • closed this issue
  • added the
    question
    label
Author
Owner

@AEPKILL commented on GitHub (Nov 22, 2022):

What is Remix? Can you provide a reproducible demo? Because I don't quite understand this demand.

<!-- gh-comment-id:1323695989 --> @AEPKILL commented on GitHub (Nov 22, 2022): What is Remix? Can you provide a reproducible demo? Because I don't quite understand this demand.
Author
Owner

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

This is Remix: https://github.com/remix-run/remix/discussions/4599

For a reproducible demo, run:

npx create-remix@latest --template remix-run/indie-stack blog-tutorial
Then, to run the app:

npm run dev

Confirm that the logs look good. Then stop the server, run npm i devtools-detector, and then import it anywhere in the project. Bam, your logs will be full of 20,000 lines of JSON object from performance.checker.ts on every request.

<!-- gh-comment-id:1329514215 --> @jdempcy commented on GitHub (Nov 28, 2022): This is Remix: https://github.com/remix-run/remix/discussions/4599 For a reproducible demo, run: ```npx create-remix@latest --template remix-run/indie-stack blog-tutorial``` Then, to run the app: ```npm run dev``` Confirm that the logs look good. Then stop the server, run `npm i devtools-detector`, and then import it anywhere in the project. Bam, your logs will be full of 20,000 lines of JSON object from performance.checker.ts on every request.
Author
Owner

@AEPKILL commented on GitHub (Dec 2, 2022):

Maybe fixed, Please try install devtools-detector@2.0.14

<!-- gh-comment-id:1334858410 --> @AEPKILL commented on GitHub (Dec 2, 2022): Maybe fixed, Please try install devtools-detector@2.0.14
Author
Owner

@jdempcy commented on GitHub (Dec 14, 2022):

Looks like that fixed it! Thank you so much AEPKILL!

<!-- gh-comment-id:1350206354 --> @jdempcy commented on GitHub (Dec 14, 2022): Looks like that fixed it! Thank you so much AEPKILL!
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/devtools-detector#30
No description provided.