`npm run watch` equivalent with SvelteKit

[houdinigraphql]

`npm run watch` equivalent with SvelteKit

[AlecAivazis]

Hey @georgecrawford!

This is something I'm definitely interested in (both the smarter writing logic, and the watch behavior). Atm running generate replaces the environment file in a way that vite really doesn't like so i frequently have to restart the dev server while working on the example. It's a big thorn in my side haha.

I think it would be a great improvement to the generation logic to see if the existing file matches what would be written and only update the necessary files - i just haven't gotten to it yet. If you wanted to try to add it, I'd love to review a PR.

[georgecrawford]

I could certainly take a look. Could you point me to the code locations from which the various files are written?

…

________________ George

On 17 Jun 2021, at 20:56, Alec Aivazis ***@***.***> wrote:  Hey @georgecrawford! This is something I'm definitely interested in. Atm running generate replaces the environment file in a way that vite really doesn't like so i frequently have to restart vite while working on the example. It's a big thorn in my side haha. I think it would be a great improvement to the generation logic to see if the existing file matches what would be written and only update the necessary files - i just haven't gotten to it yet. If you wanted to try to add it, I'd love to review a PR. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe.

[AlecAivazis]

Yea, absolutely! Anything that's generated from the compiler comes from this directory. At the moment, there are three things that are written to disk: the artifacts for the documents found in a project, the type definitions, and the runtime.

Let me know if you need any other guidance. Probably worth mentioning you can always reach out to me on the Svelte discord if you prefer chatting there.

[georgecrawford]

I’m not hugely familiar with lerna or yarn workspaces. Could you list the steps I need to run after cloning the repo to get the example working with the local version of houdini please?

…

________________ George

On 17 Jun 2021, at 23:25, Alec Aivazis ***@***.***> wrote:  Yea, absolutely! Anything that's generated from the compiler comes from this directory. At the moment, there are three things that are written to disk: the artifacts for the documents found in a project, the type definitions, and the runtime. Let me know if you need any other guidance. Probably worth mentioning you can always reach out to me on the Svelte discord if you prefer chatting there. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe.

[georgecrawford]

I've got houdini working from the local repo checkout - some combination of yarn and npm install, and npm link. So I'll take a look at only writing changed files now.

[georgecrawford]

@AlecAivazis This approach seems to work well for me. WDYT? #97

[georgecrawford]

PR was merged, thanks @AlecAivazis!