[docs] ES6 Import patterns and relative paths

[andrewmclagan]

This is most likely not and issue and just needs more documentation?

I list my components under relative paths such as: src/components/index.js with NODE_ENV=./src making the following possible: import { MyComponent } from 'components';

When the component under test includes another sub-component from index.js Jest throws various errors as it steps into the index.js file and picks up ALL my components.

jest.unmock('../MyComponent'); //

import { MyComponent } from '../MyComponent';

// ... tests below ...

Where MyComponent imports a sub-component as such:

// file: `MyComponent`

import 'SubComponent' from 'components';

// ... component code below

Is there a way to get around this situation where Jest tries to import ALL the components in an index file rather then just what is needed for the test purpose?

[andrewmclagan]

could be related to #973 and default exports? reopening this issue as there seems allot of confusion around es6 imports/exports and how babel-jest is interpreting them?

[cpojer]

Can you provide a repository that highlights this issue? I'll take a look asap next week when I return from my vacation.

[cpojer]

I don't understand how you are using the NODE_ENV variable. It is supposed to contain values like production or dev or test. Jest actually sets it if it isn't explicitly specified and it is what makes unmock work together with import. If you set it to a path, it will not work properly with Jest.

If this turns out to be a Jest issue after fixing your setup, please provide a repository that shows this issue and I will reopen and fix this bug.

[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.