Skip to content
This repository has been archived by the owner on Jan 26, 2019. It is now read-only.

Reload doesn't work on file with error when using yarn #148

Closed
pierre-H opened this issue Aug 22, 2017 · 5 comments
Closed

Reload doesn't work on file with error when using yarn #148

pierre-H opened this issue Aug 22, 2017 · 5 comments

Comments

@pierre-H
Copy link

Is this a bug report?

yes

Can you also reproduce the problem with npm 4.x?

yes

Which terms did you search for in User Guide?

I tried https://github.com/facebookincubator/create-react-app/blob/master/packages/react-scripts/template/README.md#npm-start-doesnt-detect-changes

Environment

  1. npm ls react-scripts-ts (if you haven’t ejected): 2.6.0
  2. node -v: 8.4.0
  3. npm -v: 5.3.0
  4. yarn --version (if you use Yarn): 0.27.5

Then, specify:

  1. Operating system: Windows 7 - 32bits

Steps to Reproduce

(Write your steps here:)

  1. create-react-app my-app --scripts-version=react-scripts-ts
  2. yarn start in my-app folder

Expected Behavior

When I edit and save a file which contains a TS error, it should reload automatically.

Actual Behavior

Nothing.
If I edit another file, it compiles again but the error is still there.

I tried with WebStorm and VS Code. I also followed https://github.com/facebookincubator/create-react-app/blob/master/packages/react-scripts/template/README.md#npm-start-doesnt-detect-changes

Solution

When I use npm start instead of yarn, it works.

Thank you !

@wmonk
Copy link
Owner

wmonk commented Sep 7, 2017

Hi, have you got any further with this issue?/

@pierre-H
Copy link
Author

pierre-H commented Sep 7, 2017

Very strange : I tried today with yarn, and it's working perfectly !
So I close this issue until I find another useful information ...

@pierre-H pierre-H closed this as completed Sep 7, 2017
@dmbaranov
Copy link

Have the same issue.. Once I have a typescript error, I need to restart process manually. Tried both with yarn 1.6.0 and npm 6.0

@SeedyROM
Copy link

@dmbaranov Did you ever find a solution? I'm still experiencing this bug in late December 2018.

@dmbaranov
Copy link

@SeedyROM no, not really. I don't actually use this project anymore.

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

4 participants