-
Notifications
You must be signed in to change notification settings - Fork 447
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How to use with target="es6"? #58
Comments
What version of node you are using? And why do you use |
@Igmat, sorry, forgot to mention, updated the question. By setting |
It's strange that it shows |
@Igmat did you have a change to have a look at my repro? Just in case: |
@dziamid, sorry, I was too busy at this weekend. I'll take a look and will answer tomorrow. |
@dziamid, first of all, problem isn't in ATL. Actually webpack and its loaders aren't executed while testing. First problem is caused by Second problem is caused by Third problem is caused by your import H1 from 'components/H1'; doesn't seem to be supported by P.S. |
Ok, while here is no responses, I think my last comment helped you to fix it. I'll create related TODO issues in order to find a workaround and may be even provide some changes to |
First time user here. I seemed to have had a similar (?) issue with imports when I accidentally mangled my Jest config to omit |
@niedzielski I'm slightly confused. Is the issue about the import token error or cache invalidation? |
@kulshekhar, sorry for the late response. The import issue appeared at the time to come from a missing |
I use https://github.com/s-panferov/awesome-typescript-loader instead of ts-loader, which speeds up compilation.
My current tsconfig.json is:
And my jest config is:
So my tests obviously fail with
SyntaxError: Unexpected token import
.How to handle this setup with ts-jest?
node: v.6.6.0
typescript: 2.0.8
ts-jest: 17.0.0
The text was updated successfully, but these errors were encountered: