You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -251,7 +251,7 @@ Limits the number of returned entries to the specified amount. Accepts an intege
251
251
252
252
## Query within your app ❓❓
253
253
254
-
[Check out the playground for an example](https://github.com/FlatbreadLabs/flatbread/tree/main/playground) of using Flatbread with SvelteKit to safely shoot off GraphQL queries using a static (or node) adapter.
254
+
[Check out the example integrations](https://github.com/FlatbreadLabs/flatbread/tree/main/playground) of using Flatbread with frameworks like SvelteKit and Next.js.
255
255
256
256
## Field overrides
257
257
@@ -306,8 +306,10 @@ Clone the entire monorepo! Once you've installed dependencies with `pnpm -w i`,
306
306
307
307
This will run a dev server across packages in the monorepo
308
308
309
+
You may need to seed this with a `pnpm build` first, as there can be a race condition with parallel type generation. After that, you can automatically & incrementally build changes with:
310
+
309
311
```bash
310
-
pnpm -w dev
312
+
pnpm dev
311
313
```
312
314
313
315
## **working on a package** ⚒️
@@ -317,13 +319,12 @@ Open another **terminal** tab.
317
319
| ☝️ Keep the dev server running in your other tab |
### Option 1: use the Playground as a demo project
322
+
### Option 1: use the SvelteKit example as a demo project
321
323
322
324
This allows you to work in the full context of a Flatbread instance as an end-user would, except you can tinker with the `packages` internals.
323
325
324
326
```bash
325
-
cd playground
326
-
pnpm dev
327
+
pnpm play
327
328
```
328
329
329
330
This is a good option when you want to test without creating temporary clutter per-package that you wouldn't want to commit.
@@ -344,14 +345,12 @@ node dist/index.mjs # ya need Node v16+
344
345
345
346
## **build for production** 📦
346
347
347
-
This will use `tsup` to build each package linked in the monorepo unless opted out per-package.
348
+
This will use `tsup` to build each package linked in the monorepo except the integration examples.
348
349
349
350
```bash
350
351
pnpm build
351
352
```
352
353
353
354
# 📓 Sidenotes
354
355
355
-
The transpiled TS files in the [`playground`](https://github.com/FlatbreadLabs/flatbread/tree/main/playground) are being tracked in the repo to appease the Vite gods so I can develop quicker. As the project progresses, I'll likely yeet those outta here.
356
-
357
356
Huge shoutouts to [@antfu](https://github.com/antfu/) and [@sveltejs/kit](https://github.com/sveltejs/kit) for both having invaluable reference points to guide me through learning more advanced Node, Typescript, and monorepo design all in parallel during this project.
This is a [Next.js](https://nextjs.org/) project bootstrapped with [`create-next-app`](https://github.com/vercel/next.js/tree/canary/packages/create-next-app).
2
+
3
+
## Getting Started
4
+
5
+
First, run the development server:
6
+
7
+
```bash
8
+
npm run dev
9
+
# or
10
+
yarn dev
11
+
```
12
+
13
+
Open [http://localhost:3000](http://localhost:3000) with your browser to see the result.
14
+
15
+
You can start editing the page by modifying `pages/index.tsx`. The page auto-updates as you edit the file.
16
+
17
+
[API routes](https://nextjs.org/docs/api-routes/introduction) can be accessed on [http://localhost:3000/api/hello](http://localhost:3000/api/hello). This endpoint can be edited in `pages/api/hello.ts`.
18
+
19
+
The `pages/api` directory is mapped to `/api/*`. Files in this directory are treated as [API routes](https://nextjs.org/docs/api-routes/introduction) instead of React pages.
20
+
21
+
## Learn More
22
+
23
+
To learn more about Next.js, take a look at the following resources:
24
+
25
+
-[Next.js Documentation](https://nextjs.org/docs) - learn about Next.js features and API.
26
+
-[Learn Next.js](https://nextjs.org/learn) - an interactive Next.js tutorial.
27
+
28
+
You can check out [the Next.js GitHub repository](https://github.com/vercel/next.js/) - your feedback and contributions are welcome!
29
+
30
+
## Deploy on Vercel
31
+
32
+
The easiest way to deploy your Next.js app is to use the [Vercel Platform](https://vercel.com/new?utm_medium=default-template&filter=next.js&utm_source=create-next-app&utm_campaign=create-next-app-readme) from the creators of Next.js.
33
+
34
+
Check out our [Next.js deployment documentation](https://nextjs.org/docs/deployment) for more details.
0 commit comments