Allow changing the Houdini generated output directory

[endigma]

Fixes #391

Configurable output directory

This PR adds a config value to configure the output directory name for Houdini's generated files ($houdini) by default.

TODO

• fixup cmd/init to work properly
• somehow drag config into is_root_route in houdini-svelte/fsPatch
• update e2e to use .houdini
• changset?
• docs update

[changeset-bot]

🦋 Changeset detected

Latest commit: d161ec7

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 8 packages

Name	Type
houdini-adapter-static	Minor
houdini-svelte	Minor
houdini-react	Minor
houdini	Minor
houdini-plugin-svelte-global-stores	Patch
houdini-adapter-auto	Patch
houdini-adapter-cloudflare	Patch
houdini-adapter-node	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[netlify]

✅ Deploy Preview for houdini-docs-next canceled.

Name	Link
🔨 Latest commit	d161ec7
🔍 Latest deploy log	https://app.netlify.com/sites/houdini-docs-next/deploys/6741301167061700086e4247

[netlify]

✅ Deploy Preview for houdinigraphql canceled.

Name	Link
🔨 Latest commit	d161ec7
🔍 Latest deploy log	https://app.netlify.com/sites/houdinigraphql/deploys/67413011a3f5510008809df8

[SeppahBaws]

uh-oh, can you add .houdini/ to the gitignore? 😅

[endigma]

whoops

[endigma]

Running pnpm test on this branch and main results in the same 2 tests failing, and E2E is failing in GHA on build but this also succeeds locally, any insight?

[endigma]

sveltejs/kit#13002 blocks fixing the failing test properly but I can just switch the e2e to use the barrel exports. Let me know what you want done. I see a few major options on how to proceed:

• Disable the client option and merge the plumbing with $houdini as the default
• Merge as-is, making .houdini the new default and add a note to docs about using the barreled exports
• Merge, but leaving $houdini as the default for new projects
• Alternatively, could wait until the SvelteKit bug is addressed to proceed (likely gonna hit a huge merge conflict when it comes time to resurrect unless I go and fix this upstream myself ASAP)

[SeppahBaws]

We should also update the documentation site to reflect the updated config structure.

[endigma]

Tests should pass now that I've fixed the path resolving bug, and I've updated docs to the best of my knowledge, please let me know if I've done it wrong or if that docs page is somehow autogenerated.