[Bug]: Module not found using Jest but working without

[BenjD90]

Version

27.4.7

Steps to reproduce

Hello,

To reproduce the bug, simply try to import the module "eslint/use-at-your-own-risk" in a jest test, directly or indirectly.

Here a reproduction with very little (less than 10) lines of codes : https://replit.com/@BenjaminDaniel1/Eslint-use-eslintuse-at-your-own-risk-builtinRules?v=1

Thank you for your ideas to fix this,
Benjamin

Expected behavior

The module is well imported, using require.

Actual behavior

Module is "not found" when imported in a test.

Additional context

I'm using it in case of EsLint shared configuration testing.

Environment

System:
    OS: Linux 5.4 Ubuntu 20.04.3 LTS (Focal Fossa)
    CPU: (16) x64 Intel(R) Core(TM) i7-10875H CPU @ 2.30GHz
  Binaries:
    Node: 14.18.2 - /usr/local/bin/node
    Yarn: 1.22.17 - /usr/bin/yarn
    npm: 6.14.15 - /usr/local/bin/npm

[nicolo-ribaudo]

It's because Jest does not supports package exports yet. See #9771.

[SimenB]

Yeah, I think #11961 would fix this (which will be part of Jest v28). I'll try to verify when that (or something like it) lands.

But generally, #9771 is the thing that needs to be resolved 👍

[SimenB]

Yeah, tracked in #9771

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
Please note this issue tracker is not a help forum. We recommend using StackOverflow or our discord channel for questions.