Windows problem on browser-dev after updating

[kajohnsonjd]

I have run through the code and could not locate the problem. No changes to the config other than the Apollo url for my backend. Could be that I did the update incorrectly.

[leebenson]

When you say 'updating', what do you mean exactly? Did you start a new project with the CLI and copy your custom app code over, or did you update the kit from within your current project?

[kajohnsonjd]

Inside the file I moved my src code and config, deleted everything else, upgraded ReactQL and ran the CLI and then added my src back in. Glad I kep the config because it oddly didn't appear and had to add it in, but Ive double checked it against kit and it appears to be the same.

…

Sent from my iPhone

On Jun 30, 2017, at 7:37 AM, Lee Benson ***@***.***> wrote: When you say 'updating', what do you mean exactly? Did you start a new project with the CLI and copy your custom app code over, or did you update the kit from within your current project? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.

[leebenson]

If you had to add in the kit/webpack config manually, then something definitely went wrong with your update.

The official recommendation is to run reactql new in a new folder, move over your custom src, and re-add your kit and NPM packages.

Try that, and if it still doesn't work, feel free to re-open.