-
Notifications
You must be signed in to change notification settings - Fork 42
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
Add a .chromeDataDir
option to help debugging tests
#8
Conversation
What version of node + npm are you running? I've been getting the jsx issue thing on travis and could use any additional information. |
Sure, my env info is:
I have also tried:
My guess is that the problem is a dependency shift? I haven't been able to figure out what exactly is missing the plugin either. Could be babel missing the plugin or perhaps the bundler. Anecdotally, when I |
Ok, was able to repro (I think). I Hope that helps debug. |
Awesome, thanks @songawee that really does help! |
The build error should be fixed in the latest microbundle. |
Thanks for your help with this! Maybe we could try deleting the travis cache to see if that pulls in the fixed dep? - https://docs.travis-ci.com/user/caching/#Clearing-Caches. I've had success with that in circleci. ¯_(ツ)_/¯ |
Strangely, no caches are listed :/ |
Released in 2.0.0. |
This option is useful when running tests in a non-headless Chrome environment. This will allow Chrome to save user preferences between test runs. For example, one thing I often get frustrated with is that Chrome never remembers where I last left the Chrome Dev Tools. With this change, it will be in the same spot upon returning to debug tests. This also applies to other user preferences as well.
I left it as an "opt-in" rather than a default to avoid folks forgetting to add the datadir to their
.gitignore
file.I also had trouble installing this package locally. I kept getting a
Plugin 'jsx' not found
. I'm happy to further test or improve this pr.Thanks for this awesome tool!