June 22, 2022
- Support
monti
object in Meteor settings. Thekadira
object can still be used for backwards compatibility - Add
MONTI_DEBUG_AUTH_KEY
env var, which can be used instead ofKADIRA_DEBUG_AUTH_KEY
February 23, 2022
- Fix compatibility with Meteor 2.6
July 19, 2021
- Rename to montiapm:debug
- Add MontiDebug export as alias to KadiraDebug
- Replace
meteorhacks:kadira
withmontiapm:agent
- Fix compatibility with Meteor 1.11 and newer
23-March-2016
- Only add Blaze related stuff (only event tracking), if only blaze exists in the project.
15-March-2016
- Add proper FlowRouter support. Earlier it was not depended weakly. Now we've added support for flow-router-ssr as well.
11-March-2016
- Save traces and events inside a Mongo capped collection. This helps us to work with multi-host apps and remote debugging.
11-March-2016
- Track routes for kadira:flow-router. Earlier, it was meteorhacks:flow-router.
04-March-2016
- Remove blaze activity tracking.
- Correctly use performance.now()
- Remove cosmos:browserify since we are not using any npm modules in client.
- Now Kadira Debug works in production as well.
- Add check package and now it's possible to use this package with Meteor 1.2
- Fix typo
elasedTime
- Sending unique keys to determine the version of client and server side of the app. Those keys are used to detect HCR on Kadira Debug UI.
- Update kadira to 2.23.x. It has Meteor 1.2 support
- Tracking traces and time related information to build the DDP timeline
- Track eventloop blockness as a percentage. It's not very clear to reason
- Add old version removal notice. We need to do this because our older version is a different package.
- Add system metrics support
- Move project to kadira
- Set view context to autruns runs inside Templates. Fixes #7
- Allow to use apps on Firefox. Fixes #6.
- Check userAgent for string in the method
kadira.debug.getBrowserName
- Use the actual browser name as the browseId. For this we parse, the userAgent. But, we don't parse it on the client. Instead, we do it on the server. By doing that, we don't need to send some additional code to the client. (ua-parser code)
- Track live updates in a very efficient way. For now, we only track the count and collection only. We don't track fields yet.
- Fixed an issue with our use of time to send data.
- Add a set of testing covering almost all of the code base
- Fix a potential rendering issue. See #1
- Template event's event get tracked before the activity. That makes the
- Initial release without any critical issues or bugs.