leonardoventurini / meteor-devtools-evolved Goto Github PK

You can see I don't know much about each subscription, because the params column's width is cut short. I have to click on each line to see the details. But there is a lot a blank space that could be used still in the row.

Trying to debug localhost:3000 and getting this error:

Hello with the update for my application in the minimongo tab the collections remains empty, in the old version I saw the data well

I'm going through the meteor tutorial and I tried installing meteor-devtools-evolved as a Chrome extension. I have MacOS version 10.14.6. Do I need to restart the computer or is it something else?

The info logs Meteor DevTools Evolved: Initializing on the main page... and inject.js:2 Meteor DevTools Evolved: Initialized. Attempts: 1. are always inserted after every refresh. This is polluting the logs and is very annoying, enough for me to have to disable the extension when I'm not going to be using it.

Hi, first of all thank you for your work on this project. I've been a happy user of the old Devtools package for a while so updates are appreciated. I especially like the ability to search across all collections.

My question is if you have considered, and if it would make sense, to merge/integrate/collaborate on
https://github.com/JackAdams/constellation . That package is quite similar in functionality to Meteor devtools and it has a few nice benefits:

• pluggable architecture so people can add extra functionality without having it merged upstream
• a wide selection of plugins, such as Blaze template inspector, autopublish all data, session inspector, editing documents from the client side, etc
• because it is an add-on to your app, it can be used in any browser instead of having to build separate extensions for each browser

It'd be awesome if we could have one package that does everything constellation does, plus the fancy search of meteor devtool

I have a weird issue, I ran updates the other night and now I get 0 data on 1.8.1, but 1.6 still works.

My system is Ubuntu 20.04.5 LTS
Chrome v109.0.5414.119

My main chrome profile I use for dev work has the 1.8.1 version and has zero data populating it. If I use another chrome profile that still has the 1.6 version all data loads.

I've uninstalled/reinstalled the 1.8.1 version twice, but the same problem persists. I'm not sure what else to try. For now, I'm using my other profile which has the 1.6 version to keep moving forward.

When I have your extension enabled in chrome, I get this error on every page:

I know inject.js is not your package - but I just thought I'd let you know. It's not a show stopper - just extra debugging noise in my console.

I have just installed the extension and unfortunately do not see any data on any of the tabs. I have tried closing and re-opening browser and stopping and starting Meteor but did not help.

Extension: 1.8.1
Chrome: 112.0.5615.165
Meteor: 2.12
OS: Ubuntu 22.04

Please let me know what I can do to help troubleshoot.

What do you think of adding a little MiniMongo shell that supports find/findOne operations?

I'd really like this feature and can try to implement it.

While using devtools docked to the side of the screen, it's not possible to see the full display, and you need to scroll horizontally. The display should be responsive and scale nicely while in sidebar mode.

While this tool works great with connections to the server (Meteor.connection) it does not automatically list subscriptions from DDP connections to other servers.

I am not 100% sure if there is a builtin global that exposes all curerent DDP connections but if this exists it wouldn't be that hard to add them to expose their data, too. What do you think?

Version 1.8 published three days ago seems to make my application crash with error Uncaught TypeError: Cannot convert undefined or null to object. It occurred when publishing a cursor with a nested object of shape { location: { coordinates: [...values] } } if any value in the array was null.

I didn't get the error:

• if I deactivated the extension
• if the nested array values returned by the cursor didn't contain null values
• if the field containing the array wasn't present in the cursor

I must say that this issue has been very frustrating to track down, as I was trying to identify what in my own code was causing it. I never expected a Chrome extension to actually make my application crash. This Meteor issue helped me get a hint.

A site that I manage, https://bikeloudpdx.org/brainstorm/, shows an embedded map. It is blocked by Meteor DevTools Evolved 1.3 running on Chrome Version 83.0.4103.116 (Official Build) (64-bit). The page works fine when I disable the extension.

bikeloudpdx.org is NOT a Meteor site. I believe the map is embedded from some GIS system.

A few potential warnings have been proposed until now:

• The services field is visible in the Meteor.users collection.
• Client-side handling of userId.
• Meteor.settings.public contains private keys or tokens.
• Indicate that Browser Policy is active.

I can see the Performance Tab, but it doesn't show anything.

Hi, thanks for updating this package!

I just wish it wouldn't spam me with messages like this when I am debugging a non-Meteor site:

Meteor DevTools Evolved: Initializing from iframe "https://us-u.openx.net/w/1.0/pd?cc=1&plm=10&ph=e6898ebe-7fe9-4fb5-9d9b-8e0fc3013736&gdpr=0"...
chrome-extension://ibniinmoafhgbifjojidlagmggecmpgf/build/inject.js:2 Meteor DevTools Evolved: Initializing from iframe "https://us-u.openx.net/w/1.0/pd?cc=1&plm=10&ph=e6898ebe-7fe9-4fb5-9d9b-8e0fc3013736&gdpr=0"...
chrome-extension://ibniinmoafhgbifjojidlagmggecmpgf/build/inject.js:2 Meteor DevTools Evolved: Unable to find Meteor on iframe "https://us-u.openx.net/w/1.0/pd?cc=1&plm=10&ph=e6898ebe-7fe9-4fb5-9d9b-8e0fc3013736&gdpr=0"
chrome-extension://ibniinmoafhgbifjojidlagmggecmpgf/build/inject.js:2 Meteor DevTools Evolved: Unable to find Meteor on iframe "https://us-u.openx.net/w/1.0/pd?cc=1&plm=10&ph=e6898ebe-7fe9-4fb5-9d9b-8e0fc3013736&gdpr=0"

Depending on the complexity of the site it can fill up the debug buffer making it hard to find real messages.

image

I have a small Meteor project at https://github.com/gfbeqs/mongo-decimal-test that reproduces the issue

inject.js:1 Uncaught DOMException: Failed to execute postMessage on Window: function Decimal(v) {
      var e, i, t,
        x = this;

      // Decimal called without new.
      if ...<omitted>... } could not be cloned.
    at e.sendMessage (chrome-extension://ibniinmoafhgbifjojidlagmggecmpgf/build/inject.js:1:29403)
    at u (chrome-extension://ibniinmoafhgbifjojidlagmggecmpgf/build/inject.js:1:33872)
    at g (chrome-extension://ibniinmoafhgbifjojidlagmggecmpgf/build/inject.js:1:24267)
    at m (chrome-extension://ibniinmoafhgbifjojidlagmggecmpgf/build/inject.js:1:24542)
    at j (chrome-extension://ibniinmoafhgbifjojidlagmggecmpgf/build/inject.js:1:24432)```

Being able to replay a method that is added to the bookmark is a cool addition to the extension is can be extremely helpful while debugging.

Hi! Recently i recognized that my Meteor projects got very slow using chrome (in development). At first I thought it was caused by a Meteor update, however when i tried to start chrome without extensions all went back to rocket speed! Disabling one extension after the other revealed that the meteor-devtools were the reason for this. Any suggestions how to avoid this? All in all i really like meteor-devtools 👍

My project is working with Meteor devtool and Minimongo extensions, but not this one.
Any error message to track ?

I've disabled the other tools, but nothing happens also.

My stack is Meteor 1.9 + Grapher + Grapher react.

Thanks.
I was disappointing that such an useful tool wasn't keeping up-to-date.

A collection created for client-side only with new Collection(null) is not shown in the devtools. This would be very useful even if it's shown with a randomized name.

I must admit I had forgottten about this extension, but yesterday my site stopped loading in Chrome and some debugging led me to these devtool. It seems that it creates a huge amount of setTimeouts that never happen and warnings keep ackumulating in the console.
Disabling the tool removed the problems.