-
Notifications
You must be signed in to change notification settings - Fork 2
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
errors running with mochista #14
Comments
Hi @laggingreflex thanks for opening this one. I cant seem to reproduce it on my end, im also on windows 10. Can you confirm that you installed all the npm dependencies with yarn? Can you also confirm that the following scripts run correctly. npm test |
hi @laggingreflex I took a closer look. TLDR The issue is , you can re-pull and it should work The issue was that because I am including test-setup.ts it is calling injectTapEventPlugin(). index.tsx is also calling this and this seems to be a violation as it should only be called once. For the moment i have exluded index.tsx from source files with --source-files-exclude=./app/index.tsx. This is probably better as it was trying to load up the whole app. Let me know if there are still issues |
Closing due to inactivity, please feel free to re-open and we can take another crack at this, in the meantime im happy to proceed without mochista |
The error was due to mochista not being able to parse correctly the mocha.opts file (as I myself suggested here), and I think I've since fixed it (probably in laggingreflex/mochista@8c8070f) but other than it did end up working in the end. |
Nice!, Will take another look when i get some free time |
I was trying this out (feature/mochista branch) to better understand that issue laggingreflex/mochista#12 but I'm getting these errors:
Commenting out https://github.com/el-davo/webpack-react-typescript-boilerplate/blob/feature/mochista/app/index.tsx#L12 got rid of the above error but then the following error occurred:
Any idea why these errors might be occurring, or is it only at my end? I'm on Windows 10
The text was updated successfully, but these errors were encountered: