Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Transfer elastic/require-in-the-middle to the org #890

Open
trentm opened this issue Jun 27, 2024 · 9 comments
Open

Transfer elastic/require-in-the-middle to the org #890

trentm opened this issue Jun 27, 2024 · 9 comments

Comments

@trentm
Copy link

trentm commented Jun 27, 2024

Following on import-in-the-middle (IITM) being transferred to the nodejs org and discussion in today's Diagnostics WG meeting, this is a request to also move require-in-the-middle (RITM) from the Elastic org to the Node.js org. As with import-in-the-middle, this would be governed by the TSC, but delegated to the Diagnostics WG. The expectation is that there would be significant overlap in the maintainers of IITM and RITM.

require-in-the-middle is a fairly mature library for intercepting CommonJS module loading via require(...). It is widely used in the Observability/APM space -- OpenTelemetry, Elastic, Datadog (though I think they currently have a small fork), New Relic. Reasoning for wanting to donate this to a vendor-neutral org are the same as described for IITM.

/cc @nodejs/tsc @nodejs/diagnostics

Others, please indicate if you'd be interested in maintaining RITM.

@Qard
Copy link
Member

Qard commented Jun 27, 2024

SGTM. 👍🏻

@legendecas
Copy link
Member

+1

@AbhiPrasad
Copy link

I would be interested in helping maintain! Aside from the open issues are there any areas that require-in-the-middle is looking to improve/refactor in the near future?

@watson
Copy link
Member

watson commented Jul 1, 2024

Thanks for opening this issue @trentm. I'd love to help maintain the module under the Node.js org

@pichlermarc
Copy link

I'm also happy to help out with this one. 🙂

@timfish
Copy link

timfish commented Jul 5, 2024

I would be interested in helping maintain too!

@mhdawson
Copy link
Member

mhdawson commented Jul 9, 2024

+1 from me in terms of the transfer

@legendecas
Copy link
Member

This is open for three weeks. I'm reaching out to @trentm to finalize this.

@legendecas
Copy link
Member

Still in the middle of internal process.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

8 participants