You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For my application I create a symlink inside the node_modules so, I dont have to use relative paths for import, and my test looks like
import Dictionary from 'myapp/utils/Dictionary';
describe('Dictionary', () => {
it('should return the same text if no definition found', () =>{
const text = 'This is 100% not in the dictionary';
expect(Dictionary.instant(text)).toEqual(text);
});
});
Where myapp is the symlink inside the node_modules, using this way I am getting unexpected token import. If I use relative path, like ../../Dictionary everything works fine. Is it a way to achieve that? I am suspecting it has to do with the transformation config but I couldnt figure out.
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.
For my application I create a symlink inside the node_modules so, I dont have to use relative paths for import, and my test looks like
Where
myapp
is the symlink inside the node_modules, using this way I am gettingunexpected token import
. If I use relative path, like../../Dictionary
everything works fine. Is it a way to achieve that? I am suspecting it has to do with the transformation config but I couldnt figure out.My settings look like
The text was updated successfully, but these errors were encountered: