Javier Ríos

I would go with @marvinhagemeister's approach, since it enables new functionality with a simple API that can be inlined easily with the existing plugins.

> @Jabolol exactly which of all the options do you like? 😄 The option [`here`](https://github.com/denoland/fresh/issues/1602#issuecomment-1671740190) is the one I prefer. I appreciate simplicity, and the esbuild-like approach seems the one...

> [@Jabolol](https://github.com/Jabolol) Would love your help designing the metering system for this. Feel free to file more sub-issues Hello! For the first iteration of our billing strategy I was thinking...

Had a quick chat with Carl, and here's some ideas we had: - The user should be able to buy credits beforehand - The user should get warned when they're...

Haha yeah fair points! I got a bit carried away. So many exciting things to build! For v1 MVP, lets focus on: - Basic API key auth by organization -...

Closing in favor of #4527, thank u :)

We didn't manage to get it in time. Not urgent anymore, deprioritizing.

Not yet, we didn't get the test suite to work successfully with ES modules + nextjs auto-setup. Tests on prod have the problematic tests commented out.

Seems like the API schema changed greatly in between runs. Some fields do not have data anymore ``` 2025-10-28 15:12:06 +0100 - dagster - INFO - __ASSET_JOB - 7155b5f1-dc6b-4d12-8156-905c70efcb94 -...

Here is the [`dbt` model](https://models.opensource.observer/#!/model/model.opensource_observer.funding_metrics_by_project_v1) and the [materialization](https://admin-dagster.opensource.observer/runs/bdcf0952-353e-4607-96b2-498027d02d8c). All the data has been successfully deployed to production and is ready to be integrated with the frontend! cc @ryscheng