Skip to content
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

expo and jest commands don't do anything (Windows) #2306

Closed
blakew opened this issue Sep 27, 2018 · 5 comments
Closed

expo and jest commands don't do anything (Windows) #2306

blakew opened this issue Sep 27, 2018 · 5 comments

Comments

@blakew
Copy link

blakew commented Sep 27, 2018

Please see expo-cli #48

In short, expo and jest commands don't do anything on my system in v30. The simply run and exit. I have to use the following workarounds:

expo -> expo-cli

jest -> node .\\node_modules\\jest\\bin\\jest.js

I'm on Windows 10, latest node (8.12.0)

@esamelson
Copy link
Contributor

Hi @blakew - please don't double post issues across repos, it just creates more confusion and work for us. Someone will help you out on the other issue.

@blakew
Copy link
Author

blakew commented Sep 28, 2018

@esamelson I was following the doc instructions to post jest-expo issues on expo. I ran into the jest issue after posting the other issue. I also linked to minimize confusion. Hope you don't misunderstand that my intent is simply to help your team and expo users who might have this problem as well.

@esamelson
Copy link
Contributor

Hi @blakew - thanks for clarifying, and sorry I came across more brusque than I intended. It seems like the issue is with your node installation -- package names aren't being correctly recognized in the command line. Thanks for posting your workarounds.

jest-expo is actually just a set of presets that work with Expo apps, but since your issue is happening with jest itself, you may also find it fruitful to post on the actual jest repo here: https://github.com/facebook/jest

@blakew
Copy link
Author

blakew commented Sep 29, 2018

Thanks @esamelson appreciate your help. I closed the other ticket and will look into root cause with node more carefully.

@axdemelas
Copy link

axdemelas commented Oct 11, 2018

Same problem on Node v8.12.0, Windows 10

@lock lock bot added the outdated label Jun 14, 2019
@lock lock bot locked and limited conversation to collaborators Jun 14, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants