archive/rsnext
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
rsnext/examples/with-apollo/package.json

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

24 lines
511 B
JSON
Raw Normal View History

Add Apollo example (#780) * Add minimal apollo example * Update apollo example README * Update apollo example demo link in README * Fix button styles * Fix show more button * Alias demo url * Include the data field on the Apollo store when hydrating * Revert * Include the data field on the Apollo store when hydrating per tpreusse's suggestion. * Add example to faq section in README * Sort by newest; Add active state to buttons * Make optimization suggestions * Use process.browser; inline props
2017-01-22 13:27:06 +01:00
{
Clean up examples `package.json` (#27121) Clean up package.json files in the `examples` directory: - Add `private: true` - Remove `version` (because they are irrelevant for packages that are not meant to be published) - Remove `name` (because they are optional for packages that are not meant to be published, and when someone clones an example, they often rename it and the property becomes stale) - Remove `author` - Remove `description` - Remove `license` Also remove `with-dynamic-app-layout` example completely, since it does the same as `layout-component` (https://github.com/vercel/next.js/pull/27121#discussion_r668178408). ## Documentation / Examples - [x] Make sure the linting passes
2021-07-12 21:58:03 +02:00
"private": true,
Add Apollo example (#780) * Add minimal apollo example * Update apollo example README * Update apollo example demo link in README * Fix button styles * Fix show more button * Alias demo url * Include the data field on the Apollo store when hydrating * Revert * Include the data field on the Apollo store when hydrating per tpreusse's suggestion. * Add example to faq section in README * Sort by newest; Add active state to buttons * Make optimization suggestions * Use process.browser; inline props
2017-01-22 13:27:06 +01:00
"scripts": {
fix(examples): invalid `with-apollo` and `with-graphql-hooks` (#64186) ### Why? The examples `with-apollo` and `with-graphql-hooks` included outdated API endpoints and packages. This resulted in the **failed Vercel Deployment** of the examples. <details><summary>Screenshot of failed deployments</summary> <p> #### with-graphql-hooks ![Screenshot 2024-04-08 at 3 04 05 PM](https://github.com/vercel/next.js/assets/120007119/93be6aca-e408-4b93-bf6c-04d8dfc9b59c) #### with-apollo ![Screenshot 2024-04-08 at 3 05 26 PM](https://github.com/vercel/next.js/assets/120007119/4dff9e20-714c-4a12-a27d-8fae4fc5c61d) </p> </details> ### How? - Migrated examples from `pages` to `app` router and removed invalid API endpoints. - Refactored the example to a minimal template as possible with essential features. Closes #9865 #10253 #36112 --------- Co-authored-by: Sam Ko <sam@vercel.com>
2024-04-08 16:55:39 +02:00
"dev": "next dev",
Add Apollo example (#780) * Add minimal apollo example * Update apollo example README * Update apollo example demo link in README * Fix button styles * Fix show more button * Alias demo url * Include the data field on the Apollo store when hydrating * Revert * Include the data field on the Apollo store when hydrating per tpreusse's suggestion. * Add example to faq section in README * Sort by newest; Add active state to buttons * Make optimization suggestions * Use process.browser; inline props
2017-01-22 13:27:06 +01:00
"build": "next build",
fix(examples): invalid `with-apollo` and `with-graphql-hooks` (#64186) ### Why? The examples `with-apollo` and `with-graphql-hooks` included outdated API endpoints and packages. This resulted in the **failed Vercel Deployment** of the examples. <details><summary>Screenshot of failed deployments</summary> <p> #### with-graphql-hooks ![Screenshot 2024-04-08 at 3 04 05 PM](https://github.com/vercel/next.js/assets/120007119/93be6aca-e408-4b93-bf6c-04d8dfc9b59c) #### with-apollo ![Screenshot 2024-04-08 at 3 05 26 PM](https://github.com/vercel/next.js/assets/120007119/4dff9e20-714c-4a12-a27d-8fae4fc5c61d) </p> </details> ### How? - Migrated examples from `pages` to `app` router and removed invalid API endpoints. - Refactored the example to a minimal template as possible with essential features. Closes #9865 #10253 #36112 --------- Co-authored-by: Sam Ko <sam@vercel.com>
2024-04-08 16:55:39 +02:00
"start": "next start",
"lint": "next lint"
Add Apollo example (#780) * Add minimal apollo example * Update apollo example README * Update apollo example demo link in README * Fix button styles * Fix show more button * Alias demo url * Include the data field on the Apollo store when hydrating * Revert * Include the data field on the Apollo store when hydrating per tpreusse's suggestion. * Add example to faq section in README * Sort by newest; Add active state to buttons * Make optimization suggestions * Use process.browser; inline props
2017-01-22 13:27:06 +01:00
},
"dependencies": {
adopt modern & supported Apollo Client patterns in the with-apollo example (#65316) #64186 removed the pages router implementation from the `with-apollo` example and replaced it with an app router implementation. Unfortunately, it did so in an unsupported way. At this point, we can not support any streaming SSR scenario without additional helper packages - in the case of the app router, it is vital to use the `@apollo/experimental-nextjs-app-support` package. This PR switches the example to our officially supported patterns. <!-- 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 - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating 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 # -->
2024-05-27 02:08:52 +02:00
"@apollo/client": "^3.10.1",
"@apollo/experimental-nextjs-app-support": "^0.10.0",
fix(examples): invalid `with-apollo` and `with-graphql-hooks` (#64186) ### Why? The examples `with-apollo` and `with-graphql-hooks` included outdated API endpoints and packages. This resulted in the **failed Vercel Deployment** of the examples. <details><summary>Screenshot of failed deployments</summary> <p> #### with-graphql-hooks ![Screenshot 2024-04-08 at 3 04 05 PM](https://github.com/vercel/next.js/assets/120007119/93be6aca-e408-4b93-bf6c-04d8dfc9b59c) #### with-apollo ![Screenshot 2024-04-08 at 3 05 26 PM](https://github.com/vercel/next.js/assets/120007119/4dff9e20-714c-4a12-a27d-8fae4fc5c61d) </p> </details> ### How? - Migrated examples from `pages` to `app` router and removed invalid API endpoints. - Refactored the example to a minimal template as possible with essential features. Closes #9865 #10253 #36112 --------- Co-authored-by: Sam Ko <sam@vercel.com>
2024-04-08 16:55:39 +02:00
"graphql": "^16.8.1",
adopt modern & supported Apollo Client patterns in the with-apollo example (#65316) #64186 removed the pages router implementation from the `with-apollo` example and replaced it with an app router implementation. Unfortunately, it did so in an unsupported way. At this point, we can not support any streaming SSR scenario without additional helper packages - in the case of the app router, it is vital to use the `@apollo/experimental-nextjs-app-support` package. This PR switches the example to our officially supported patterns. <!-- 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 - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating 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 # -->
2024-05-27 02:08:52 +02:00
"next": "^14.2.3",
"react": "^18.3.0",
"react-dom": "^18.3.0"
fix(examples): invalid `with-apollo` and `with-graphql-hooks` (#64186) ### Why? The examples `with-apollo` and `with-graphql-hooks` included outdated API endpoints and packages. This resulted in the **failed Vercel Deployment** of the examples. <details><summary>Screenshot of failed deployments</summary> <p> #### with-graphql-hooks ![Screenshot 2024-04-08 at 3 04 05 PM](https://github.com/vercel/next.js/assets/120007119/93be6aca-e408-4b93-bf6c-04d8dfc9b59c) #### with-apollo ![Screenshot 2024-04-08 at 3 05 26 PM](https://github.com/vercel/next.js/assets/120007119/4dff9e20-714c-4a12-a27d-8fae4fc5c61d) </p> </details> ### How? - Migrated examples from `pages` to `app` router and removed invalid API endpoints. - Refactored the example to a minimal template as possible with essential features. Closes #9865 #10253 #36112 --------- Co-authored-by: Sam Ko <sam@vercel.com>
2024-04-08 16:55:39 +02:00
},
"devDependencies": {
"@types/node": "^20.12.5",
adopt modern & supported Apollo Client patterns in the with-apollo example (#65316) #64186 removed the pages router implementation from the `with-apollo` example and replaced it with an app router implementation. Unfortunately, it did so in an unsupported way. At this point, we can not support any streaming SSR scenario without additional helper packages - in the case of the app router, it is vital to use the `@apollo/experimental-nextjs-app-support` package. This PR switches the example to our officially supported patterns. <!-- 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 - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating 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 # -->
2024-05-27 02:08:52 +02:00
"@types/react": "^18.3.0",
"@types/react-dom": "^18.3.0",
fix(examples): invalid `with-apollo` and `with-graphql-hooks` (#64186) ### Why? The examples `with-apollo` and `with-graphql-hooks` included outdated API endpoints and packages. This resulted in the **failed Vercel Deployment** of the examples. <details><summary>Screenshot of failed deployments</summary> <p> #### with-graphql-hooks ![Screenshot 2024-04-08 at 3 04 05 PM](https://github.com/vercel/next.js/assets/120007119/93be6aca-e408-4b93-bf6c-04d8dfc9b59c) #### with-apollo ![Screenshot 2024-04-08 at 3 05 26 PM](https://github.com/vercel/next.js/assets/120007119/4dff9e20-714c-4a12-a27d-8fae4fc5c61d) </p> </details> ### How? - Migrated examples from `pages` to `app` router and removed invalid API endpoints. - Refactored the example to a minimal template as possible with essential features. Closes #9865 #10253 #36112 --------- Co-authored-by: Sam Ko <sam@vercel.com>
2024-04-08 16:55:39 +02:00
"typescript": "^5.4.4"
Remove `licence` from all `example/package.json` that has them (#28007) * Add licences to all example/package.json that lack them * Revert "Add licences to all example/package.json that lack them" This reverts commit 5d4e25012f7334772b8ef5924bc355277e827cba. * Update check-examples to remove `license` field from examples * Remove `license` from all examples. This was mentioned in vercel/next.js#27121 but it looks like it didn't end up being in the merge? Co-authored-by: JJ Kasper <jj@jjsweb.site>
2021-08-14 17:48:39 +02:00
}
Add Apollo example (#780) * Add minimal apollo example * Update apollo example README * Update apollo example demo link in README * Fix button styles * Fix show more button * Alias demo url * Include the data field on the Apollo store when hydrating * Revert * Include the data field on the Apollo store when hydrating per tpreusse's suggestion. * Add example to faq section in README * Sort by newest; Add active state to buttons * Make optimization suggestions * Use process.browser; inline props
2017-01-22 13:27:06 +01:00
}
Reference in a new issue Copy permalink