HarperFast
diff --git a/‎.eslintrc.json‎
Lines changed: 0 additions & 3 deletions b/‎.eslintrc.json‎
Lines changed: 0 additions & 3 deletions
diff --git a/‎.npmrc‎
Lines changed: 1 addition & 0 deletions b/‎.npmrc‎
Lines changed: 1 addition & 0 deletions
diff --git a/‎README.md‎
Lines changed: 1 addition & 2 deletions b/‎README.md‎
Lines changed: 1 addition & 2 deletions
diff --git a/‎app/layout.js‎
Lines changed: 9 additions & 2 deletions b/‎app/layout.js‎
Lines changed: 9 additions & 2 deletions
diff --git a/‎config.yaml‎
Lines changed: 2 additions & 2 deletions b/‎config.yaml‎
Lines changed: 2 additions & 2 deletions
diff --git a/‎eslint.config.mjs‎
Lines changed: 13 additions & 0 deletions b/‎eslint.config.mjs‎
Lines changed: 13 additions & 0 deletions
@@ -0,0 +1 @@
+save-exact=true
@@ -11,15 +11,14 @@ The Next.js application can interact with the database through the [Resource API
 
 1. Clone this repo locally
 2. Run `npm install`
-   1. If HarperDB is already installed on your machine (we recommend it be [installed globally](https://docs.harperdb.io/docs/getting-started#installing-a-harperdb-instance)), then run `npm link harperdb`.
 3. Run `npm run dev`
 4. Open [http://localhost:3000](http://localhost:3000) 🎉
 
 ## How does it work?
 
 This example in and of itself is a [HarperDB Component](https://docs.harperdb.io/docs/developers/components), and is reliant on the `@harperdb/nextjs` protocol extension component in order to access to the [HarperDB Globals](https://docs.harperdb.io/docs/technical-details/reference/globals). The globals are only available on server-side code paths such as [server actions](https://nextjs.org/docs/app/building-your-application/data-fetching/server-actions-and-mutations) and [server components](https://nextjs.org/docs/app/building-your-application/rendering/server-components). Any code paths using HarperDB globals must first import the `harperdb` package (i.e. `import('harperdb')`).
 
-> [!TIP] 
+> [!TIP]
 > Use the `harperdb-nextjs` CLI (part of the `@harperdb/nextjs` package) to replace the Next.js CLI. For example, `next dev` becomes `harperdb-nextjs dev`. This CLI handles running HarperDB and providing sensible configuration values for the `@harperdb/nextjs` component.
 
 Based on Next.js best practices, it is recommended to use this in **server actions** so that server _and client_ components can both access the same functions. This example demonstrates this pattern by defining two server actions, `listDogs` and `getDog` (located in [./app/actions.js](./app/actions.js)). These are then used throughout the application, in both [Client](./app/client-component.js) and [Server](./app/dogs/[id]/page.js) components!
@@ -10,7 +10,14 @@ export default function RootLayout({ children }) {
 			<body style={{ width: '500px', fontFamily: 'sans-serif' }}>
 				<header>
 					<nav>
-						<ul style={{ display: 'flex', gap: '1rem', listStyle: 'none', padding: 0 }}>
+						<ul
+							style={{
+								display: 'flex',
+								gap: '1rem',
+								listStyle: 'none',
+								padding: 0,
+							}}
+						>
 							<li>
 								<Link href="/">Home</Link>
 							</li>
@@ -29,7 +36,7 @@ export default function RootLayout({ children }) {
 
 						<p>
 							Dig into the source code here:{' '}
-							<Link href="https://github.com/HarperDB-Add-Ons/nextjs-example">HarperDB-Add-Ons/nextjs-example</Link>
+							<Link href="https://github.com/HarperDB/nextjs-example">HarperDB/nextjs-example</Link>
 						</p>
 					</section>
 					{children}
 
@@ -1,7 +1,7 @@
 graphqlSchema:
-  files: '*.graphql'
+  files: 'schema.graphql'
 jsResource:
-  files: './resources.js'
+  files: 'resources.js'
 '@harperdb/nextjs':
   package: '@harperdb/nextjs'
   files: '/*'
@@ -0,0 +1,13 @@
+import { FlatCompat } from '@eslint/eslintrc';
+
+const compat = new FlatCompat({
+	baseDirectory: import.meta.dirname,
+});
+
+const eslintConfig = [
+	...compat.config({
+		extends: ['next/core-web-vitals', 'prettier'],
+	}),
+];
+
+export default eslintConfig;