update pnpmlock

.changeset/tricky-mangos-brake.md

@@ -0,0 +1,5 @@
+---
+'houdini': patch
+---
+
+add onError hook

.changeset/tricky-schools-rescue.md

@@ -0,0 +1,5 @@
+---
+'houdini': patch
+---
+
+refactoring to use directly vite-plugin-watch-and-run

.changeset/twenty-crabs-admire.md

@@ -0,0 +1,5 @@
+---
+'houdini': patch
+---
+
+add `quietQueryError` config value to supress all query errors

.github/pull_request_template.md

@@ -1,11 +1,10 @@
-## Will fix
-- #
+Fixes #TICKET
+
+### To help everyone out, please make sure your PR does the following:
+
+- [ ] Update the first line to point to the ticket that this PR fixes
+- [ ] Add a message that clearly describes the fix
+- [ ] If applicable, add a test that would fail without this fix
+- [ ] Make sure the unit and integration tests pass locally with `pnpm run tests` and `cd integration && pnpm run tests`
+- [ ] Includes a changeset if your fix affects the user with `pnpm changeset`
 
-## Some highlights
-- [ ] New tests are passing
-  - [ ]
-  - [ ]
-- [ ] New settings are available
-  - [ ]
-  - [ ]
-- [ ] The doc has been updated

integration/package.json

@@ -17,7 +17,6 @@
     "format": "prettier --ignore-path .gitignore --write --plugin-search-dir=. ."
   },
   "devDependencies": {
-    "@kitql/vite-plugin-watch-and-run": "^0.4.0",
     "@playwright/test": "1.25.0",
     "@replayio/playwright": "0.2.23",
     "@sveltejs/adapter-auto": "1.0.0-next.66",

integration/src/lib/utils/routes.ts

@@ -29,6 +29,7 @@ export const routes = {
   Plugin_query_component: '/plugin/query/component',
   Plugin_query_beforeLoad: '/plugin/query/beforeLoad',
   Plugin_query_afterLoad: '/plugin/query/afterLoad',
+  Plugin_query_onError: '/plugin/query/onError',
   Plugin_query_layout: '/plugin/query/layout',
 
   Plugin_mutation_mutation: '/plugin/mutation/mutation',

integration/src/routes/plugin/query/onError/+page.svelte

@@ -0,0 +1,8 @@
+<script lang="ts">
+  import type { PageData } from './$houdini';
+  export let data: PageData;
+</script>
+
+<div id="result">
+  {data.fancyMessage}
+</div>

integration/src/routes/plugin/query/onError/+page.ts

@@ -0,0 +1,16 @@
+import { graphql } from '$houdini';
+import type { OnErrorEvent } from './$houdini';
+
+export const houdini_load = graphql`
+  query PreprocessorOnErrorTestQuery {
+    user(id: "1000", snapshot: "preprocess-on-error-test-simple") {
+      name
+    }
+  }
+`;
+
+export const onError = ({ error, input }: OnErrorEvent) => {
+  return {
+    fancyMessage: 'hello'
+  };
+};

integration/src/routes/plugin/query/onError/spec.ts

@@ -0,0 +1,11 @@
+import { test } from '@playwright/test';
+import { routes } from '../../../../lib/utils/routes.js';
+import { expectToBe, goto } from '../../../../lib/utils/testsHelper.js';
+
+test.describe('query preprocessor', () => {
+  test('onError hook', async ({ page }) => {
+    await goto(page, routes.Plugin_query_onError);
+
+    await expectToBe(page, 'hello');
+  });
+});

package.json

@@ -112,7 +112,7 @@
 		"@babel/parser": "^7.17.2",
 		"@graphql-tools/schema": "^8.3.7",
 		"@kitql/helper": "^0.3.4",
-		"@kitql/vite-plugin-watch-and-run": "^0.4.2",
+		"vite-plugin-watch-and-run": "^1.0.1",
 		"@types/memory-fs": "^0.3.3",
 		"babylon": "^7.0.0-beta.47",
 		"commander": "^7.1.0",

site/src/routes/api/config.svx

@@ -32,6 +32,7 @@ It can contain the following values:
 - `schemaPollHeaders` (optional): An object specifying the headers to use when pulling your schema. Keys of the object are header names and its values can be either a strings or a function that takes the current `process.env` and returns the the value to use. If you want to access an environment variable, prefix your string with `env:`, ie `env:API_KEY`.
 - `schemaPollInterval` (optional, default: `2000`): Configures the schema polling behavior for the kit plugin. If its value is greater than `0`, the plugin will poll the set number of milliseconds. If set to `0`, the plugin will only pull the schema when you first run `dev`. If you set to `null`, the plugin will never look for schema changes. You can see use the [pull-schema command] to get updates.
 - `globalStorePrefix` (optional, default: `GQL_`): The default prefix of your global stores. This lets your editor provide autocompletion with just a few characters.
+- `quietQueryErrors` (optional, default: `false`): With this enabled, errors in your query will not be thrown as exceptions. You will have to handle error state in your route components or by hand in your load (or the onError hook)
 
 ## Custom Scalars
 

site/src/routes/api/routes.svx

@@ -111,7 +111,7 @@ A query store holds an object with the following fields that accessed like `$sto
 
 - `data` contains the result of the query. It's value will update as mutations, subscriptions, and other queries provide more recent information.
 - `loading` contains the loading state (`true` or `false`) for a query found outside of a route component (ie, not defined in `src/routes`)
-- `errors` contains any error values that occur for a query found outside of a route component (ie, not defined in `src/routes`)
+- `errors` contains any error values that occur for a query found outside of a route component (ie, not defined in `src/routes`). If you want to use this for managing your errors, you should enable the [quietQueryError](/api/config) configuration option.
 - `partial` contains a boolean that indicates if the result has a partial match
 
 ### Methods
@@ -239,6 +239,28 @@ export function afterLoad({ data }) {
 }
 ```
 
+#### `onError`
+
+If defined, the load function will invoked this function instead of throwing an error when an error is received.  
+It receives three inputs: the load event, the inputs for each query, and the error that was encountered. Just like
+the other hooks, `onError` can return an object that provides props to the route.
+
+```javascript
+// src/routes/myRoute/+page.js
+
+export const houdini_load = graphql`
+	query MyProfile {
+		profile {
+			name
+		}
+	}
+`
+
+export function onError({ error }) {
+	throw this.redirect(307, '/login')
+}
+```
+
 ### Disabling Inline Query Loading
 
 Sometimes it's useful to have a lazy query that only fires when you call `fetch` (for
@@ -298,7 +320,7 @@ export async function load(event) {
 }
 ```
 
-<DeepDive title="Loading multiple stores simulatenously">
+<DeepDive title="Loading multiple stores simultaneously">
 
 Be careful when loading multiple stores at once.
 

site/src/routes/guides/faq.svx

@@ -17,13 +17,18 @@ Yep! You can use queries or any document anywhere you can use a svelte store. Ju
 Yes! You'll just have to rely on the store apis for your documents and write your route's loads manually.
 For more information on using your document's stores check out [Working with GraphQL](/guides/working-with-graphql) guide.
 
+### Are `+server` files supported?
+
+Unforunately, `+server` have additional constraints that make them a unique challenge to support (not impossible, just tricky). This is also an area of SvelteKit that is
+rapidly changing and so we are opting to not officially support `+server` files until things stabilize a bit more. Sorry for the inconvinience!
+
 ### What's the best way to build a Full-Stack application with SvelteKit?
 
 Simple answer, we recommend [KitQL](https://www.kitql.dev/). It gives you everything you need when building a full-stack application with GraphQL (including [Houdini](https://www.houdinigraphql.com/) of course 😉). For more information about our collaboration, head over to this [blog post](https://www.the-guild.dev/blog/houdini-and-kitql).
 
 ### How does the plugin generate loads?
 
-Curious how this works under the hook? Consider this query:
+Consider this query:
 
 ```svelte
 <!-- src/routes/myRoute/+page.svelte -->
@@ -83,6 +88,12 @@ If you haven't seen Houdini's document stores before, please check out the [Work
 You should use the `metadata` parameter in the document store to pass arbitrary information into your client's network function. For more information,
 please visit [the query store docs](/api/query/store#passing-metadata).
 
+### What is this `Generated an empty chunk...` warning from vite?
+
+If you have a route directory that does not contain a `+page.js` file and do not have an inline query in your `+page.svelte`, the
+plugin will generate an empty `+page.js` file that is never used. This confuses vite hence the warning. Don't worry - this empty
+file is never imported if you don't have an inline query so there's no performance implication.
+
 ### My IDE is complaining that the internal directives and fragments don't exist.
 
 Every plugin and editor is different so we can't give you an exact answer but Houdini will write a file inside of the `$houdini` directory that contains all of the custom definitions that it relies on. Be default this file is located at `$houdini/graphql/schema.graphql` and `$houdini/graphql/documents.gql`. You can configure this value in your [config file](/api/config) under the `definitionsPath` value.

site/src/routes/guides/migrating-to-016.svx

@@ -154,6 +154,18 @@ the store itself and do not need the `$`:
   </button>
 ```
 
+`afterLoad` hooks also now take the whole load event as a single `event` parameter:
+
+```diff
+- export async function afterLoad({ params, data }) {
++ export async function afterLoad({ event, data }) {
+    return {
+-     message: params.message
++     message: event.params.message
+    }
+  }
+```
+
 ### 2.b Inline Fragments
 
 The order for the arguments to inline fragments has been inverted.

site/src/routes/guides/setting-up-your-project.svx

@@ -93,8 +93,26 @@ this, add the following block of code to `src/routes/+layout.svelte` and any nam
 
 ### Svelte
 
-While your exact situation might change, somehow you should import houdini's preprocessor and pass it to your
-svelte config
+If you are building a vanilla svelte project, you will have to configure the compiler and preprocessor to generate the correct logic by setting the `framework`
+field in your config file to `"svelte"`.
+
+If you are using vite, you should use the `houdini/vite` plugin even if
+you aren't using kit. Update your `vite.config.js` file to look like this:
+
+```javascript
+// vite.config.js
+
+import { defineConfig } from 'vite'
+import { svelte } from '@sveltejs/vite-plugin-svelte'
+import houdini from 'houdini/vite'
+
+export default defineConfig({
+	plugins: [houdini(), svelte()]
+})
+```
+
+If you aren't using vite, it's a lot harder to give an exact recommendation but somehow
+you should import houdini's preprocessor and pass it to your svelte config
 
 ```javascript
 // svelte.config.js
@@ -105,10 +123,6 @@ export default {
 }
 ```
 
-You also have to configure the compiler and preprocessor to generate the correct logic by setting the `framework`
-field in your config file to `"svelte"`. If you are using vite, you should use the `houdini/vite` plugin even if
-you aren't using kit.
-
 Please keep in mind that returning the response from a query, you should not rely on `this.redirect` to handle the
 redirect as it will update your browsers `location` attribute, causing a hard transition to that url. Instead, you should
 use `this.error` to return an error and handle the redirect in a way that's appropriate for your application.

src/cmd/generators/kit/index.ts

@@ -59,6 +59,7 @@ export default async function svelteKitGenerator(config: Config, docs: Collected
 
 			const afterLoad = scriptExports.includes('afterLoad')
 			const beforeLoad = scriptExports.includes('beforeLoad')
+			const onError = scriptExports.includes('onError')
 
 			// we need to create a typescript file that has a definition of the variable and hook functions
 			const typeDefs = `import type * as Kit from '@sveltejs/kit';
@@ -106,7 +107,7 @@ type AfterLoadData = {
 		.join(', \n')}
 }
 
-type AfterLoadInput = {
+type LoadInput = {
 	${queries
 		.filter((query) => query.variableDefinitions?.length)
 		.map((query) => {
@@ -122,7 +123,7 @@ type AfterLoadInput = {
 export type AfterLoadEvent = {
 	event: PageLoadEvent
 	data: AfterLoadData
-	input: AfterLoadInput
+	input: LoadInput
 }
 `
 		: ''
@@ -138,7 +139,16 @@ type BeforeLoadReturn = ReturnType<typeof import('./+page').beforeLoad>;
 `
 		: ''
 }
+${
+	onError
+		? `
+
+export type OnErrorEvent =  { event: LoadEvent, input: LoadInput, error: Error | Error[] }
 
+type OnErrorReturn = ReturnType<typeof import('./+page').onError>;
+`
+		: ''
+}
 
 export type PageData = {
 	${queries
@@ -148,7 +158,9 @@ export type PageData = {
 			return [name, name + config.storeSuffix].join(': ')
 		})
 		.join(', \n')}
-} ${afterLoad ? '& AfterLoadReturn ' : ''} ${beforeLoad ? '& BeforeLoadReturn ' : ''}
+} ${afterLoad ? '& AfterLoadReturn ' : ''} ${beforeLoad ? '& BeforeLoadReturn ' : ''} ${
+				onError ? '& OnErrorReturn ' : ''
+			} 
 
 `