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

caching issue #7

Closed
scf4 opened this issue Jun 11, 2017 · 2 comments
Closed

caching issue #7

scf4 opened this issue Jun 11, 2017 · 2 comments

Comments

@scf4
Copy link

scf4 commented Jun 11, 2017

There seems to be some sort of caching going on. It doesn't seem to realize the .graphql file has changed unless I rename the filename.

I've had this happen on 3 separate projects.

@zvictor
Copy link
Contributor

zvictor commented Jun 12, 2017

Is it something different than what we described in the Caveats section?

Babel does not track dependency between imported and importing files after the transformation is made. Therefore, you need to change the importing file in order to see your changes in the imported file spread.

@jlengstorf
Copy link

jlengstorf commented Jul 12, 2017

It's not different from what was described, but it's a pretty big source of confusion when working on a team. Is this something that could be configurable? I don't know enough about Babel internals to know if this is easy/feasible, but it would be a huge help for working with .graphql files, for example.

I just read the next line in the Caveats section:

To overcome this, you can:

  • Disable babel cache (BABEL_DISABLE_CACHE=1)

That was all I needed. Thanks!

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

3 participants