Invoice #252995 to Aurelia
Insights package development
Paid
Invoice #252995
Maintenance and Development
Submitted by Dwayne Charrington•Approved by Dwayne Charrington
Jun 7, 2025
Expense Details
Invoice items
Scaffolding and initial project setup (1.5hrs). Creating a new `@aurelia/insights` package within the existing monorepo structure.
$150.00 USD
Core lifecycle hooks implementation (5hrs). Implementing core logic to intercept and measure core lifecycle events `creating`, `hydrating`, `hydrated`, `binding`, `bound`, `attaching`, `attached`, `detaching` and `detached`. Measuring distance between jumps in lifecycle methods. This involved creating the performance tracking abstraction for the browser performance API, ensuring meaningful metrics were being tracked between measurements. This underwent a few different approaches before settling on measured means between lifecycles.
$250.00 USD
Router lifecycle hooks support (6 hours). Extension of monitoring capabilities to track timing of router events in both core `@aurelia/router` and `@aurelia/router-lite` packages.
$300.00 USD
Filtering and noise reduction logic (5 hours). Designed and implemented the configuraiton API to allow developers to filter out specific components by name and other filtering criteria to eliminate spam being produce by metrics tracking in the plugin.
$250.00 USD
Utilities and abstraction logic for debugging, aggregating and more (6 hours). Developing utility functions for debugging, aggregating and working with the performance data thinking beyond the performance tab in dev tools.
$300.00 USD
.NET core style telemetry implementation (6 hours). Architecting and implementing a flexible telemtry system for custom event tracking inspired by .NET Core's implementation.
$300.00 USD
Writing comprehensive documentation (5 hours). Wrote and edited extensive documentation that covers all facets of the plugin including; installation, configuration, best practices, use cases and examples.
$250.00 USD
Extensive unit testing (8 hours). Unit testing the entire package including core services, components, configuration and other facets. The testing has also been used as a means of guiding the development of the package by identifying code that was hard to test or flaky and allowing realtime refactoring throughout development.
$400.00 USD
Event listener measuring implementation (3 hours). Measuring performance of long-running event listeners in templates.
$150.00 USD
Dashboard and UI components for visualising performance data outside of performance tab (7 hours). The initial plugin development centred around the performance tab in devtools and then was expanded to allow for more meaningful tracking and display of performance and other metrics data in the plugin as the performance tab was not suitable for this purpose.
$350.00 USD
Total amount $2,700.00 USD
Additional Information
payout method
PayPal
Email address
********
Collective balance
Expense policies
Expense policies
We process expenses twice a week after an admin of the Collective has approved them. We make payments via PayPal and Bank Transfer (using Wise) and can only make payouts to countries served by these payment processors. You are not required to upload an invoice document (the data you submit in the expense form is sufficient), but if you would like to include an uploaded invoice, please make it out to:
Collective Name, Open Source Collective, 440 N. Barranca Avenue #3939, Covina, CA 91723, USA
INFORMATION REQUIRED ON EXPENSES:
Please refer to the documentation here for payment processing requirements on reimbursements and invoices.
REFUNDS:
If you would like a refund, please email [email protected] with the transaction #, the collective you donated to, the date, and the amount of the transaction.
FAQ
How do I get paid from a Collective?
Submit an expense and provide your payment information.
How are expenses approved?
Collective admins are notified when an expense is submitted, and they can approve or reject it.
Is my private data made public?
No. Only the expense amount and description are public. Attachments, payment info, emails and addresses are only visible to you and the admins.
When will I get paid?
Payments are processed by the Collective's Fiscal Host, the organization that hold funds on their behalf. Many Fiscal Hosts pay expenses weekly, but each one is different.
Why do you need my legal name?
The display name is public and the legal name is private, appearing on receipts, invoices, and other official documentation used for tax and accounting purposes.
Collective balance
$39,026.67 USDFiscal Host:
Open Source Collective