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

Using with version expo 36 #18

Closed
DanielNugent opened this issue Feb 20, 2020 · 1 comment
Closed

Using with version expo 36 #18

DanielNugent opened this issue Feb 20, 2020 · 1 comment

Comments

@DanielNugent
Copy link

Expected Behavior

The expo client starts properly

Please describe the behavior you are expecting

Current Behavior

The client crashes

What is the current behavior?

Failure Information (for bugs)

expo start
Starting project at D:\Downloads\argon-react-native-master\argon-react-native-master
Expo DevTools is running at http://localhost:19002
Opening DevTools in the browser... (press shift-d to disable)
error Invalid regular expression: /(.\fixtures\.|node_modules[\]react[\]dist[\].|website\node_modules\.|heapCapture\bundle.js|.\tests\.)$/: Unterminated character class.

Metro Bundler process exited with code 1
Set EXPO_DEBUG=true in your env to view the stack trace.

Steps to Reproduce

Have version 36 of the expo cli installed.

Context

  • Device: PC
  • Operating System: W10
  • Browser and Version: Chrome

expo start
Starting project at D:\Downloads\argon-react-native-master\argon-react-native-master
Expo DevTools is running at http://localhost:19002
Opening DevTools in the browser... (press shift-d to disable)
error Invalid regular expression: /(.\fixtures\.|node_modules[\]react[\]dist[\].|website\node_modules\.|heapCapture\bundle.js|.\tests\.)$/: Unterminated character class.

Metro Bundler process exited with code 1
Set EXPO_DEBUG=true in your env to view the stack trace.

@palingheorghe
Copy link
Contributor

Hi @DanielNugent ! Thank you for your interest in our products! You can find out more about this error here: facebook/react-native#26969 . This is an issue with react-native/node version and not with our app. I suggest to reinstall the product with a clear cache first and then try fixing the issue.

Thanks,
Alin

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants