feat: Extend ESM hooks options for iitm v1.10.0

[timfish]

import-in-the-middle@1.10.0 supports regular expressions for include and exclude.

Is there a risk here that users might not have the latest version of import-in-the-middle in their dependencies?

[mydea]

Hmm yeah, users will OOTB not get an updated version of this. One thing we could do I guess is add an import-in-the-middle dependency ourselves for ^1.10.0? Does that make sense? 🤔 That may help sometimes if users dedupe correctly, but I guess even then it may not work for some scenarios to force updating this to latest 🤔

[mydea]

FWIW this is possibly also the reason why some users report that using exclude / import is not working for them - they may be "stuck: on 1.8.1 which is the minimum version required by otel 🤯

[timfish]

add an import-in-the-middle dependency ourselves for ^1.10.0? Does that make sense?

Since we actually register import-in-the-middle/hook.mjs as our hook, this is probably a good idea!

[mydea]

I think you need to run yarn and commit the lockfile? Also FWIW I notice that when we do this it still keeps the 1.8.1 version in our lockfile :( need to deduplicate the lockfile to get a consistent version :( but better than nothing, I guess!

[timfish]

import-in-the-middle@1.10.0 supports regular expressions for include and exclude.

Is there a risk here that users might not have the latest version of import-in-the-middle in their dependencies?

[mydea]

Hmm yeah, users will OOTB not get an updated version of this. One thing we could do I guess is add an import-in-the-middle dependency ourselves for ^1.10.0? Does that make sense? 🤔 That may help sometimes if users dedupe correctly, but I guess even then it may not work for some scenarios to force updating this to latest 🤔

[mydea]

FWIW this is possibly also the reason why some users report that using exclude / import is not working for them - they may be "stuck: on 1.8.1 which is the minimum version required by otel 🤯

[timfish]

add an import-in-the-middle dependency ourselves for ^1.10.0? Does that make sense?

Since we actually register import-in-the-middle/hook.mjs as our hook, this is probably a good idea!

[mydea]

I think you need to run yarn and commit the lockfile? Also FWIW I notice that when we do this it still keeps the 1.8.1 version in our lockfile :( need to deduplicate the lockfile to get a consistent version :( but better than nothing, I guess!

[timfish]

import-in-the-middle@1.10.0 supports regular expressions for include and exclude.

Is there a risk here that users might not have the latest version of import-in-the-middle in their dependencies?

[mydea]

Hmm yeah, users will OOTB not get an updated version of this. One thing we could do I guess is add an import-in-the-middle dependency ourselves for ^1.10.0? Does that make sense? 🤔 That may help sometimes if users dedupe correctly, but I guess even then it may not work for some scenarios to force updating this to latest 🤔

[mydea]

FWIW this is possibly also the reason why some users report that using exclude / import is not working for them - they may be "stuck: on 1.8.1 which is the minimum version required by otel 🤯

[timfish]

add an import-in-the-middle dependency ourselves for ^1.10.0? Does that make sense?

Since we actually register import-in-the-middle/hook.mjs as our hook, this is probably a good idea!

[mydea]

I think you need to run yarn and commit the lockfile? Also FWIW I notice that when we do this it still keeps the 1.8.1 version in our lockfile :( need to deduplicate the lockfile to get a consistent version :( but better than nothing, I guess!

[timfish]

import-in-the-middle@1.10.0 supports regular expressions for include and exclude.

Is there a risk here that users might not have the latest version of import-in-the-middle in their dependencies?

[mydea]

Hmm yeah, users will OOTB not get an updated version of this. One thing we could do I guess is add an import-in-the-middle dependency ourselves for ^1.10.0? Does that make sense? 🤔 That may help sometimes if users dedupe correctly, but I guess even then it may not work for some scenarios to force updating this to latest 🤔

[mydea]

FWIW this is possibly also the reason why some users report that using exclude / import is not working for them - they may be "stuck: on 1.8.1 which is the minimum version required by otel 🤯

[timfish]

add an import-in-the-middle dependency ourselves for ^1.10.0? Does that make sense?

Since we actually register import-in-the-middle/hook.mjs as our hook, this is probably a good idea!

[mydea]

I think you need to run yarn and commit the lockfile? Also FWIW I notice that when we do this it still keeps the 1.8.1 version in our lockfile :( need to deduplicate the lockfile to get a consistent version :( but better than nothing, I guess!

[timfish]

import-in-the-middle@1.10.0 supports regular expressions for include and exclude.

Is there a risk here that users might not have the latest version of import-in-the-middle in their dependencies?

[mydea]

Hmm yeah, users will OOTB not get an updated version of this. One thing we could do I guess is add an import-in-the-middle dependency ourselves for ^1.10.0? Does that make sense? 🤔 That may help sometimes if users dedupe correctly, but I guess even then it may not work for some scenarios to force updating this to latest 🤔

[mydea]

FWIW this is possibly also the reason why some users report that using exclude / import is not working for them - they may be "stuck: on 1.8.1 which is the minimum version required by otel 🤯

[timfish]

add an import-in-the-middle dependency ourselves for ^1.10.0? Does that make sense?

Since we actually register import-in-the-middle/hook.mjs as our hook, this is probably a good idea!

[mydea]

I think you need to run yarn and commit the lockfile? Also FWIW I notice that when we do this it still keeps the 1.8.1 version in our lockfile :( need to deduplicate the lockfile to get a consistent version :( but better than nothing, I guess!

[timfish]

import-in-the-middle@1.10.0 supports regular expressions for include and exclude.

Is there a risk here that users might not have the latest version of import-in-the-middle in their dependencies?

[mydea]

Hmm yeah, users will OOTB not get an updated version of this. One thing we could do I guess is add an import-in-the-middle dependency ourselves for ^1.10.0? Does that make sense? 🤔 That may help sometimes if users dedupe correctly, but I guess even then it may not work for some scenarios to force updating this to latest 🤔

[mydea]

FWIW this is possibly also the reason why some users report that using exclude / import is not working for them - they may be "stuck: on 1.8.1 which is the minimum version required by otel 🤯

[timfish]

add an import-in-the-middle dependency ourselves for ^1.10.0? Does that make sense?

Since we actually register import-in-the-middle/hook.mjs as our hook, this is probably a good idea!

[mydea]

I think you need to run yarn and commit the lockfile? Also FWIW I notice that when we do this it still keeps the 1.8.1 version in our lockfile :( need to deduplicate the lockfile to get a consistent version :( but better than nothing, I guess!

[timfish]

import-in-the-middle@1.10.0 supports regular expressions for include and exclude.

Is there a risk here that users might not have the latest version of import-in-the-middle in their dependencies?

[mydea]

Hmm yeah, users will OOTB not get an updated version of this. One thing we could do I guess is add an import-in-the-middle dependency ourselves for ^1.10.0? Does that make sense? 🤔 That may help sometimes if users dedupe correctly, but I guess even then it may not work for some scenarios to force updating this to latest 🤔

[mydea]

FWIW this is possibly also the reason why some users report that using exclude / import is not working for them - they may be "stuck: on 1.8.1 which is the minimum version required by otel 🤯

[timfish]

add an import-in-the-middle dependency ourselves for ^1.10.0? Does that make sense?

Since we actually register import-in-the-middle/hook.mjs as our hook, this is probably a good idea!

[mydea]

I think you need to run yarn and commit the lockfile? Also FWIW I notice that when we do this it still keeps the 1.8.1 version in our lockfile :( need to deduplicate the lockfile to get a consistent version :( but better than nothing, I guess!

[timfish]

import-in-the-middle@1.10.0 supports regular expressions for include and exclude.

Is there a risk here that users might not have the latest version of import-in-the-middle in their dependencies?

[mydea]

Hmm yeah, users will OOTB not get an updated version of this. One thing we could do I guess is add an import-in-the-middle dependency ourselves for ^1.10.0? Does that make sense? 🤔 That may help sometimes if users dedupe correctly, but I guess even then it may not work for some scenarios to force updating this to latest 🤔

[mydea]

FWIW this is possibly also the reason why some users report that using exclude / import is not working for them - they may be "stuck: on 1.8.1 which is the minimum version required by otel 🤯

[timfish]

add an import-in-the-middle dependency ourselves for ^1.10.0? Does that make sense?

Since we actually register import-in-the-middle/hook.mjs as our hook, this is probably a good idea!

[mydea]

I think you need to run yarn and commit the lockfile? Also FWIW I notice that when we do this it still keeps the 1.8.1 version in our lockfile :( need to deduplicate the lockfile to get a consistent version :( but better than nothing, I guess!