Doesn't resolve with babel-plugin-module-resolver files in SFCs

A component that imports from an alias with babel-plugin-module-resolver will fail to resolve in jest. Seems like it’s not resolving ./ as the babel cwd, but from the component location.

Example

.babelrc:

{
  "plugins": [
    ["module-resolver", { "alias": { "@": "src/components" } } ]
  ]
}

src/components/A.vue:

<template>
  <p>{{ text }}</p>
</template>

<script>
export default {
  data() {
    return {
      text: 'hi'
    }
  }
};
</script>

src/components/B.vue:

<template>
  <ComponentA />
</template>

<script>
import ComponentA from '@/A.vue';

export default {
  components: { ComponentA }
};
</script>

Result:

  ● Test suite failed to run

    Cannot find module './src/components/A.vue' from 'B.vue'
      
      at Resolver.resolveModule (node_modules/jest-resolve/build/index.js:191:17)
      ...

[txantslusam]

Can confirm this bug. I have a component, which import another one from different directory. Importing this component with @ alias results in: Cannot find module './src/components/partials/B' from 'A.vue' But when i change import path to relative path, eg. '../../components/partials/B' it resolves correctly. I added moduleNameMapper to Jest and configure babel alias.

[pmesgari]

Hi @eddyerburgh As we spoke before, today I started working on debugging this issue. So far I have found out that using alias in .babelrc file will result in jest to look for the module as a hastePackage which results in the error. Without the alias nothing is being searched for as a hastePackage.

I am looking to find out what is a hastePackage in jest, I was wondering if you or someone else has any ideas on this?