feat(node): Allow to pass registerEsmLoaderHooks to preload

[mydea]

As mentioned in here: #12912 (comment) there is no way today to exclude/include esm modules when preloading today.

This PR adds the option to pass registerEsmLoaderHooks as option to preloadOpenTelemetry, which allows to exclude/include packages there as well. Users can then write their own custom preload script and configure this there, if wanted.

Naming

I chose to use the same option naming here than for init, although the semantics are a bit different - here we can't actually disable the wrapping (because that's the only reason to even call this). We can also use a different name if we want, but I thought this would maybe be easier to understand that this is the same thing 🤔

[Lms24]

LGTM and agree on keeping the name aligned with the init option.

Users can then write their own custom preload script and configure this there, if wanted.

Sounds fair, given this won't be a widely used option. We should just make sure to document this because right now, we only show how to set integrations and debug via env variables.

[mydea]

As mentioned in here: #12912 (comment) there is no way today to exclude/include esm modules when preloading today.

This PR adds the option to pass registerEsmLoaderHooks as option to preloadOpenTelemetry, which allows to exclude/include packages there as well. Users can then write their own custom preload script and configure this there, if wanted.

Naming

I chose to use the same option naming here than for init, although the semantics are a bit different - here we can't actually disable the wrapping (because that's the only reason to even call this). We can also use a different name if we want, but I thought this would maybe be easier to understand that this is the same thing 🤔

[Lms24]

LGTM and agree on keeping the name aligned with the init option.

Users can then write their own custom preload script and configure this there, if wanted.

Sounds fair, given this won't be a widely used option. We should just make sure to document this because right now, we only show how to set integrations and debug via env variables.

[mydea]

As mentioned in here: #12912 (comment) there is no way today to exclude/include esm modules when preloading today.

This PR adds the option to pass registerEsmLoaderHooks as option to preloadOpenTelemetry, which allows to exclude/include packages there as well. Users can then write their own custom preload script and configure this there, if wanted.

Naming

I chose to use the same option naming here than for init, although the semantics are a bit different - here we can't actually disable the wrapping (because that's the only reason to even call this). We can also use a different name if we want, but I thought this would maybe be easier to understand that this is the same thing 🤔

[Lms24]

LGTM and agree on keeping the name aligned with the init option.

Users can then write their own custom preload script and configure this there, if wanted.

Sounds fair, given this won't be a widely used option. We should just make sure to document this because right now, we only show how to set integrations and debug via env variables.

[mydea]

As mentioned in here: #12912 (comment) there is no way today to exclude/include esm modules when preloading today.

This PR adds the option to pass registerEsmLoaderHooks as option to preloadOpenTelemetry, which allows to exclude/include packages there as well. Users can then write their own custom preload script and configure this there, if wanted.

Naming

I chose to use the same option naming here than for init, although the semantics are a bit different - here we can't actually disable the wrapping (because that's the only reason to even call this). We can also use a different name if we want, but I thought this would maybe be easier to understand that this is the same thing 🤔

[Lms24]

LGTM and agree on keeping the name aligned with the init option.

Users can then write their own custom preload script and configure this there, if wanted.

Sounds fair, given this won't be a widely used option. We should just make sure to document this because right now, we only show how to set integrations and debug via env variables.

[mydea]

As mentioned in here: #12912 (comment) there is no way today to exclude/include esm modules when preloading today.

This PR adds the option to pass registerEsmLoaderHooks as option to preloadOpenTelemetry, which allows to exclude/include packages there as well. Users can then write their own custom preload script and configure this there, if wanted.

Naming

I chose to use the same option naming here than for init, although the semantics are a bit different - here we can't actually disable the wrapping (because that's the only reason to even call this). We can also use a different name if we want, but I thought this would maybe be easier to understand that this is the same thing 🤔

[Lms24]

LGTM and agree on keeping the name aligned with the init option.

Users can then write their own custom preload script and configure this there, if wanted.

Sounds fair, given this won't be a widely used option. We should just make sure to document this because right now, we only show how to set integrations and debug via env variables.

[mydea]

As mentioned in here: #12912 (comment) there is no way today to exclude/include esm modules when preloading today.

This PR adds the option to pass registerEsmLoaderHooks as option to preloadOpenTelemetry, which allows to exclude/include packages there as well. Users can then write their own custom preload script and configure this there, if wanted.

Naming

I chose to use the same option naming here than for init, although the semantics are a bit different - here we can't actually disable the wrapping (because that's the only reason to even call this). We can also use a different name if we want, but I thought this would maybe be easier to understand that this is the same thing 🤔

[Lms24]

LGTM and agree on keeping the name aligned with the init option.

Users can then write their own custom preload script and configure this there, if wanted.

Sounds fair, given this won't be a widely used option. We should just make sure to document this because right now, we only show how to set integrations and debug via env variables.

[mydea]

As mentioned in here: #12912 (comment) there is no way today to exclude/include esm modules when preloading today.

This PR adds the option to pass registerEsmLoaderHooks as option to preloadOpenTelemetry, which allows to exclude/include packages there as well. Users can then write their own custom preload script and configure this there, if wanted.

Naming

I chose to use the same option naming here than for init, although the semantics are a bit different - here we can't actually disable the wrapping (because that's the only reason to even call this). We can also use a different name if we want, but I thought this would maybe be easier to understand that this is the same thing 🤔

[Lms24]

LGTM and agree on keeping the name aligned with the init option.

Users can then write their own custom preload script and configure this there, if wanted.

Sounds fair, given this won't be a widely used option. We should just make sure to document this because right now, we only show how to set integrations and debug via env variables.

[mydea]

As mentioned in here: #12912 (comment) there is no way today to exclude/include esm modules when preloading today.

This PR adds the option to pass registerEsmLoaderHooks as option to preloadOpenTelemetry, which allows to exclude/include packages there as well. Users can then write their own custom preload script and configure this there, if wanted.

Naming

I chose to use the same option naming here than for init, although the semantics are a bit different - here we can't actually disable the wrapping (because that's the only reason to even call this). We can also use a different name if we want, but I thought this would maybe be easier to understand that this is the same thing 🤔

[Lms24]

LGTM and agree on keeping the name aligned with the init option.

Users can then write their own custom preload script and configure this there, if wanted.

Sounds fair, given this won't be a widely used option. We should just make sure to document this because right now, we only show how to set integrations and debug via env variables.