tsc-watch fails to restart node server on source file changes within a docker bind mount about tsc-watch HOT 12 CLOSED

Hi @anthonyorona ! I have actually not that big of an idea how the typescript watcher works under the hood, but I had the same issue that my changes on the typescript files on a Windows Host didn't trigger any tsc-watch rebuilds inside my docker container based on the node image (weird thing though, is that it worked for me approximately a year ago, so no Idea what changed in the meantime, be it docker bind mounts, tsc --watch or tsc-watch). Probably similar to you, file changes were correctly mirrored into the docker container, but the typescript watcher just didn't get triggered.

However, even though it is probably a less CPU friendly way, things worked for me as soon as I've explicitly set the watchOptions' watchFile & watchDirectory tsconfig settings to one of the "polling" settings likes fixedpollinginterval, prioritypollinginterval etc. (https://www.typescriptlang.org/tsconfig#watch-watchFile). So e.g. following in the tsconfig file worked then:

{
  ...
  "watchOptions": {
    "watchFile": "dynamicprioritypolling",
    "watchDirectory": "dynamicprioritypolling",
    "excludeDirectories": ["**/node_modules", "dist"],
  }
}

from tsc-watch.

the problem persists, this issue needs to be reopened, it seems like tsc-watch is not working properly with docker's container anymore

from tsc-watch.

To narrow down the problem, can you just run it with tsc --watch without any hot reload. does it work?

from tsc-watch.

@anthonyorona Can you confirm @oelerpearler's solution?

from tsc-watch.

Bump before closing

from tsc-watch.

@YouneLL @anthonyorona Can any of you provide an example of the failure?

from tsc-watch.

There is no failure, tsc-watch simply doesn't restart after files have changed.

from tsc-watch.

Can someone please provide an example?

from tsc-watch.

This is my workaround:

tsconfig.json

{
  // ...
  "watchOptions": {
    "excludeDirectories": ["**/node_modules", "dist"]
  },
}

Dockerfile

# ...
CMD npm run dev -- --watchFile dynamicPriorityPolling --watchDirectory dynamicPriorityPolling

I wasn't able to use Dockers exec form, it somehow messes up arguments

from tsc-watch.

@gilamran
I'd say that this may be reproduced for any project using tsc-watch on Docker.

Maybe synced changes don't trigger native file events within container that typescript relies on by default.

This may be also Windows host - only issue as I'm on Windows 10

Related issue: microsoft/TypeScript#54144

from tsc-watch.

yea, ok so the reason is probably what @piotr-cz mentioned: microsoft/TypeScript#54144
tsc-watch is relaying on tsc to do the actual watch. If it's not working for typescript it work for tsc-watch

from tsc-watch.