lookup: add import-in-the-middle

[bengl]

Ref: nodejs/TSC#1397

I believe all the requirements are met. The module has 1,778,787 weekly downloads on npm and uses loaders, which AFAIK no others in lookup.json do.

Checklist

• contribution guidelines followed
  here

[codecov-commenter]

Codecov Report

Patch coverage has no change and project coverage change: +0.18 🎉

Comparison is base (dd3b422) 96.27% compared to head (992cdb0) 96.46%.

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #953      +/-   ##
==========================================
+ Coverage   96.27%   96.46%   +0.18%     
==========================================
  Files          28       28              
  Lines        2149     2149              
==========================================
+ Hits         2069     2073       +4     
+ Misses         80       76       -4     

see 1 file with indirect coverage changes

☔ View full report in Codecov by Sentry.
📢 Do you have feedback about the report comment? Let us know in this issue.

[targos]

Here's a first test run: https://github.com/nodejs/citgm/actions/runs/5219659418

[targos]

Should we skip on Windows? It looks like the tests cannot be run on that platform

[bengl]

@targos that's odd. AFAICT it passes on Windows in import-in-the-middle's CI. https://github.com/DataDog/import-in-the-middle/actions/runs/5218109352

[richardlau]

@targos that's odd. AFAICT it passes on Windows in import-in-the-middle's CI. https://github.com/DataDog/import-in-the-middle/actions/runs/5218109352

That's running a different npm script (test-win) for Windows. I'm not sure we have the ability in CITGM to invoke different scripts on a per-platform basis.

[bengl]

@targos @richardlau I've published import-in-the-middle@1.4.1 which no longer has a windows-specific test command, so npm test ought to work everywhere now.

[bengl]

For whatever reason it still seems to fail with citgm, despite passing in import-in-the-middle's CI on Windows. I added "skip": "win32" for now, but I can take another shot at removing that at a future date (and a future PR).

[mhdawson]

LGTM

[targos]

Windows tests are known to be flaky: #930