rsnext/examples/with-grafbase
Karl Horky 3ad55721d1
Remove incorrect entries for pnpm debug log (#47241)
**Reasons for making this change:**

- it is contained within `node_modules/`, which is already ignored
- the previous versions, which were not in `node_modules/`, did not have
a period at the beginning of the filename

Links to documentation supporting these rule changes:

**Changelog with proof here:**


ba4b2db1f2/pnpm/CHANGELOG.md (L3330)

History:

- my PR to remove this from `github/gitignore` here:
https://github.com/github/gitignore/pull/4250
- First introduced in `github/gitignore` in
https://github.com/github/gitignore/pull/3732 by `@sakurayang` (merged
by `@martinwoodward`)

<!-- Thanks for opening a PR! Your contribution is much appreciated.
To make sure your PR is handled as smoothly as possible we request that
you follow the checklist sections below.
Choose the right checklist for the change(s) that you're making:

## For Contributors

### Improving Documentation or adding/fixing Examples

- The "examples guidelines" are followed from our contributing doc
https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md
- Make sure the linting passes by running `pnpm build && pnpm lint`. See
https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md

### Fixing a bug

- Related issues linked using `fixes #number`
- Tests added. See:
https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs
- Errors have a helpful link attached, see
https://github.com/vercel/next.js/blob/canary/contributing.md

### Adding a feature

- Implements an existing feature request or RFC. Make sure the feature
request has been accepted for implementation before opening a PR. (A
discussion must be opened, see
https://github.com/vercel/next.js/discussions/new?category=ideas)
- Related issues/discussions are linked using `fixes #number`
- e2e tests added
(https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs
- Documentation added
- Telemetry added. In case of a feature if it's used or not.
- Errors have a helpful link attached, see
https://github.com/vercel/next.js/blob/canary/contributing.md



## For Maintainers

- Minimal description (aim for explaining to someone not on the team to
understand the PR)
- When linking to a Slack thread, you might want to share details of the
conclusion
- Link both the Linear (Fixes NEXT-xxx) and the GitHub issues
- Add review comments if necessary to explain to the reviewer the logic
behind a change

### What?

### Why?

### How?

Closes NEXT-
Fixes #

-->

---------

Co-authored-by: JJ Kasper <jj@jjsweb.site>
2023-03-26 22:26:05 -07:00
..
.vscode feat(examples): with-grafbase (#42898) 2022-11-15 19:18:31 +01:00
app feat(examples): use experimental edge runtime with grafbase (#42992) 2022-11-17 14:02:55 -08:00
gql feat(examples): with-grafbase (#42898) 2022-11-15 19:18:31 +01:00
grafbase feat(examples): with-grafbase (#42898) 2022-11-15 19:18:31 +01:00
lib feat(examples): use experimental edge runtime with grafbase (#42992) 2022-11-17 14:02:55 -08:00
.env.local.example feat(examples): with-grafbase (#42898) 2022-11-15 19:18:31 +01:00
.gitignore Remove incorrect entries for pnpm debug log (#47241) 2023-03-26 22:26:05 -07:00
codegen.ts feat(examples): with-grafbase (#42898) 2022-11-15 19:18:31 +01:00
next-env.d.ts Remove incorrect entries for pnpm debug log (#47241) 2023-03-26 22:26:05 -07:00
next.config.js feat(examples): use experimental edge runtime with grafbase (#42992) 2022-11-17 14:02:55 -08:00
package.json feat(examples): with-grafbase (#42898) 2022-11-15 19:18:31 +01:00
postcss.config.js feat(examples): with-grafbase (#42898) 2022-11-15 19:18:31 +01:00
README.md feat(examples): use experimental edge runtime with grafbase (#42992) 2022-11-17 14:02:55 -08:00
tailwind.config.js feat(examples): with-grafbase (#42898) 2022-11-15 19:18:31 +01:00
tsconfig.json feat(examples): with-grafbase (#42898) 2022-11-15 19:18:31 +01:00

Next.js with Grafbase

This example shows to use Grafbase with Next.js. This example features fetching from a local GraphQL backend powered by the Grafbase CLI, and GraphQL Code Generator for making type-safe queries.

Demo

You can see a demo of this online at https://nextjs-rsc-demo.grafbase-vercel.dev.

Deploy to Vercel

Make sure to provide your GRAFBASE_API_URL and GRAFBASE_API_KEY to Vercel as environment variables when deploying.

Deploy with Vercel

How to use

Execute create-next-app with npm, Yarn, or pnpm to bootstrap the example:

npx create-next-app --example with-grafbase with-grafbase-app
yarn create next-app --example with-grafbase with-grafbase-app
pnpm create next-app --example with-grafbase with-grafbase-app

To run the example locally you need to:

  1. Copy the .env.local.example to .env.local and provide your API URL and API Key: cp .env.local.example .env.local — the defaults will be fine for development mode.

  2. Run the Grafbase CLI using npx grafbase@latest dev

  3. Populate the backend with some Post entries using a GraphQL mutation:

mutation {
  postCreate(
    input: {
      title: "I love Next.js!"
      slug: "i-love-nextjs"
      comments: [{ create: { message: "me too!" } }]
    }
  ) {
    post {
      id
      slug
    }
  }
}
  1. Run the app locally and go to http://localhost:3000 to navigate to each post page! This data is fetched from the local backend.

  2. Optionally run npm run codegen to watch for any changes to queries inside of the app and automatically generate types.

Learn more