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-cli on windows will crash when file cannot be imported instead of showing error #21148

Open
SleeplessByte opened this issue Feb 10, 2023 · 1 comment
Labels
CLI Versioned Expo CLI -- `npx expo start` Issue accepted

Comments

@SleeplessByte
Copy link

Summary

Related to #21147 but a different issue.

  • When an import error occurs, a module loader error occurs
  • This bubbles up
  • Windows tries to attach debugging information via C:\DumpStack.log.tmp
  • Chokidar watches this change (it REALLY should not!)
  • It will never be able to acquire a lock
  • Everything will hang.

Note that this can also result in errors eventually such as #17547.

What platform(s) does this occur on?

No response

SDK Version

47

Environment

  expo-env-info 1.0.5 environment info:
    System:
      OS: Windows 10 10.0.22621
    Binaries:
      Node: 16.19.0 - ~\scoop\apps\nvm\current\nodejs\nodejs\node.EXE
      Yarn: 1.22.19 - ~\scoop\apps\nvm\current\nodejs\nodejs\yarn.CMD
      npm: 8.19.3 - ~\scoop\apps\nvm\current\nodejs\nodejs\npm.CMD
    npmPackages:
      @expo/webpack-config: ^0.17.2 => 0.17.4
      expo: ~47.0.12 => 47.0.13
      react: 18.1.0 => 18.1.0
      react-dom: 18.1.0 => 18.1.0
      react-native: 0.70.5 => 0.70.5
      react-native-web: ~0.18.9 => 0.18.12
    Expo Workflow: managed

Minimal reproducible example

https://github.com/XPBytes/issue-cli-no-import-no-error

@SleeplessByte SleeplessByte added CLI Versioned Expo CLI -- `npx expo start` needs validation Issue needs to be validated labels Feb 10, 2023
@brentvatne brentvatne added Issue accepted and removed needs validation Issue needs to be validated labels Feb 10, 2023
@expo-bot
Copy link
Collaborator

Thank you for filing this issue!
This comment acknowledges we believe this may be a bug and there’s enough information to investigate it.
However, we can’t promise any sort of timeline for resolution. We prioritize issues based on severity, breadth of impact, and alignment with our roadmap. If you’d like to help move it more quickly, you can continue to investigate it more deeply and/or you can open a pull request that fixes the cause.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CLI Versioned Expo CLI -- `npx expo start` Issue accepted
Projects
None yet
Development

No branches or pull requests

3 participants