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

Changes in a .graphql file doesn't recompile automatically #5744

Closed
glennreyes opened this issue Nov 7, 2018 · 2 comments
Closed

Changes in a .graphql file doesn't recompile automatically #5744

glennreyes opened this issue Nov 7, 2018 · 2 comments

Comments

@glennreyes
Copy link
Contributor

glennreyes commented Nov 7, 2018

Is this a bug report?

Yes

Did you try recovering your dependencies?

Yes

Which terms did you search for in User Guide?

graphql, import, reload

Environment

Environment Info:

  System:
    OS: macOS 10.14
    CPU: x64 Intel(R) Core(TM) i7-6567U CPU @ 3.30GHz
  Binaries:
    Node: 11.1.0 - /usr/local/bin/node
    Yarn: 1.12.1 - /usr/local/bin/yarn
    npm: 6.4.1 - /usr/local/bin/npm
  Browsers:
    Chrome: 70.0.3538.77
    Firefox: 61.0.1
    Safari: 12.0
  npmPackages:
    react: ^16.6.1 => 16.6.1 
    react-dom: ^16.6.1 => 16.6.1 
    react-scripts: 2.1.1 => 2.1.1 
  npmGlobalPackages:
    create-react-app: Not Found

Steps to Reproduce

  1. Install following deps:
yarn add graphql.macro graphql
  1. Add src/test.graphql:
type Query {
  hello: String
}
  1. Import graphql file:
import { loader } from 'graphql.macro'
const test = loader('./test.graphql')
  1. Add changes to src/test.graphql, eg replace content with:
type Query {
  bye: String
}

Expected Behavior

Bundler recompiles / App reloads

Actual Behavior

Bundler does not recompile / App does not reload

Reproducible Demo

https://codesandbox.io/s/z6yjkp4l4m

Please download from codesandbox since it's only reproducible locally.

Related: #5076, #4893, #3909, #1792

@iansu
Copy link
Contributor

iansu commented Nov 9, 2018

I don't think any of the related issues you listed are related to this specific problem. I think this is more applicable: #5580

@Timer
Copy link
Contributor

Timer commented Nov 20, 2018

Closing as dupe of #5580.

@Timer Timer closed this as completed Nov 20, 2018
@lock lock bot locked and limited conversation to collaborators Jan 9, 2019
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

3 participants