Support being initialized after imports about home HOT 4 CLOSED

Can you be a little more specific, @atrauzzi, about how you think Glimpse might interfere with the use of an IoC? Even with an IoC, there should still be a single entry point from which Glimpse can be require()'d and initialized. After that point, it shouldn't matter how/when other component's packages are require()'d as Glimpse instruments packages lazily.

(The reason Glimpse must be initialized first is so that it can setup a hook to listen for other packages being imported, at which point it will add the appropriate instrumentation. If your application doesn't (explicitly or implicitly) import a package that Glimpse instruments, instrumentation of that package will not occur.)

from home.

My original thought was to do with module hoisting, optimization and just making sure no code has to be run before the module graph is complete.

This may or may not be an issue, but might merit consideration as the init call is a statement.

from home.

Feel free to give Glimpse a try in such a project and let us know if you run into any issues, as we definitely want Glimpse to work in as many scenarios as possible. Otherwise, if you can point to a project with an IoC similar to yours, we can experiment with adding Glimpse to the project ourselves and see how it behaves.

from home.

I think I'll be able to deliver that in a little bit. I'll close this ticket now and return later if possible with a repo link.

from home.