Restarting but not receiving changes for some extensions about babel-watch HOT 3 CLOSED

Hi - the issue seems to be that the babel plugin embeds the definition of test.graphql into main.js. Dependencies from one file to another are not tracked and are not usually present in Babel. You can see that the definition changes correctly once you re-save main.ts.

You can run with DEBUG="babel-watch:*" npm start to see the full inner workings of babel-watch.

There is no way to avoid this in the current code. It is tempting to add a --no-cache option or similar, but doing so would essentially make this the same as running nodemon with @babel/register, as the cache is what makes babel-watch worthwhile.

I'm going to close this as a use case we can't support, unfortunately.

from babel-watch.

So essentially babel is caching it, not babel-watch? And because babel doesn't know that main.ts depends on the GraphQL file, it doesn't rebuild main.ts? Am I understanding this correctly?

babel-plugin-import-graphql has a runtime option, but it doesn't do anything as far as I tested it. I am going to open an issue there.

On a side note: Could you please look at the pull request I opened a few weeks ago? It's a totally different topic but I think it's useful and would be curious what you think about it.

from babel-watch.

babel-watch is caching it, by file. But while it invalidates the test.graphql cache, the reality is that main.js contains test.graphql, so removing the cache does nothing.

from babel-watch.