Lee Robinson
5536526826
Remove dotenv from Relay example. ( #21814 )
...
Address one of the bullet points from https://github.com/vercel/next.js/issues/15225 to remove unused dependencies on `dotenv` now that it's supported by default in Next.js.
2021-02-03 19:33:51 +00:00
Robin
c47f3d84c4
Unify installation scripts for example apps ( #19808 )
2021-01-24 17:05:49 +01:00
Luis Alvarez D
e28fd50441
Include utm_source on example links to vercel.com ( #21305 )
2021-01-19 07:28:54 +00:00
Luc Leray
8eaabe2fb0
Fix deploy buttons URLs ( #20834 )
...
Fix all deploy button URLs in the Next.js repo to follow the following format:
```
https://vercel.com/new/git/external?repository-url=https://github.com/vercel/next.js/tree/canary/examples/ <EXAMPLE_NAME>&project-name=<EXAMPLE_NAME>&repository-name=<EXAMPLE_NAME>
```
The detailed docs for the Deploy Button can be found here: https://vercel.com/docs/more/deploy-button .
Also updates legacy Vercel import flow URLs (starting with vercel.com/import or with vercel.com/new/project), to use the new vercel.com/new URLs.
---
For example, for the `hello-world` example:
The URL is https://vercel.com/new/git/external?repository-url=https://github.com/vercel/next.js/tree/canary/examples/hello-world&project-name=hello-world&repository-name=hello-world
And the deploy button looks like this:
[![Deploy with Vercel](https://vercel.com/button )](https://vercel.com/new/git/external?repository-url=https://github.com/vercel/next.js/tree/canary/examples/hello-world&project-name=hello-world&repository-name=hello-world )
---
For reference, I used the following regexes to search for the incorrect URLs
```
\(https://vercel.com/import/git\?s=https://github.com/vercel/next.js/tree/canary/examples/(.*) \)
\(https://vercel.com/import/git\?c=1&s=https://github.com/vercel/next.js/tree/canary/examples/ ([^&]*)(.*)\)
\(https://vercel.com/import/project\?template=https://github.com/vercel/next.js/tree/canary/examples/(.*) \)
https://vercel.com/import/git
https://vercel.com/import/select-scope
https://vercel.com/import
https://vercel.com/new/project
```
2021-01-07 01:40:29 +00:00
Jens Meindertsma
a3c47721a1
Include all files in Prettier ( #17050 )
...
This uses the "Expand directories" feature introduces in Prettier 2.0 to automatically format all supported file types.
Also, I fixed some badly formatted files.
2020-09-14 02:53:19 +00:00
Kristoffer K
2acb53bd30
chore: update example names to match their folders ( #16268 )
...
**What's the problem this PR addresses?**
A decent amount of the examples don't have a `name` field in `package.json` that matches their folder name, meaning they either lack a name or the names are duplicated.
I was testing Yarn 2 workspaces using the entire examples directory and needed to get rid of the duplicates.
**How did you fix it?**
Updated the names to match the names of their folders
2020-09-05 21:23:51 +00:00
Luis Alvarez D
4162e39696
Undo unrequired readme changes done to examples ( #16831 )
...
Related to https://github.com/vercel/next.js/pull/16678#issuecomment-684962496
2020-09-03 19:11:58 +00:00
Joe Haddad
f17d435166
Ensure all examples are MIT licensed ( #16691 )
2020-08-29 22:32:35 -04:00
NorbertLuszkiewicz
c03d4931de
Simplify example usage instructions ( #16678 )
...
Co-authored-by: Joe Haddad <joe.haddad@zeit.co>
2020-08-29 22:22:02 -04:00
Flavian Desverne
f9cb5ac6b0
Replace Graphcool with dedicated example GraphQL server using Prisma ( #15752 )
...
## Motivation
As Graphcool is being shutdown, we replaced all the graphcool api endpoints with some handcrafted APIs using Prisma & Nexus, that can be found here https://github.com/prisma-labs/nextjs-graphql-api-examples . These GraphQL endpoints are now deployed to Vercel.
## Notes
- I couldn't get the reason-relay example to run. Given that the relay endpoint works on the other relay example, I don't see any reason why it wouldn't work on that one
- The `with-apollo` example is buggy when creating some posts, but nothing related to the switch of the api endpoint as it was already buggy before. I suspect the `concatPagination` strategy to be the cause of that bug, but I couldn't figure it out.
Fixes #14780
2020-08-05 06:26:54 +00:00
Pierre de la Martinière
0729394ee1
Update next-transpile-modules in all examples ( #15739 )
...
Should prevent some tears when people tries to replicate some example with Next.js 9.5.0 ;)
cheers!
2020-07-31 15:53:53 +00:00
Tanmay Laud
f00ad581a1
Added .gitignore to examples that are deployed to vercel ( #15127 )
...
Co-authored-by: Joe Haddad <joe.haddad@zeit.co>
2020-07-16 10:52:23 -04:00
Joe Haddad
4a12fb0a5f
Normalize example gitignores ( #13768 )
...
This removes a bunch of unnecessary `.gitignore`s and fixes some CMS examples that don't ignore `node_modules` etc.
2020-06-04 20:39:52 +00:00
Joe Haddad
7d038dfef1
Suggest npx
over npm init
( #13637 )
...
This updates old examples to the more universal `npx` command.
Fixes https://github.com/vercel/next.js/discussions/12103
2020-06-01 17:36:57 +00:00
Joe Haddad
db5b5a76a8
Update some examples to Vercel ( #13477 )
...
Co-authored-by: kodiakhq[bot] <49736102+kodiakhq[bot]@users.noreply.github.com>
2020-05-28 13:32:29 +02:00
Joe Haddad
b7e17e09e5
Update references to zeit/next.js ( #13463 )
2020-05-27 17:51:11 -04:00
Tim Neutkens
e4d22cec63
Fix formatting of older PR that passed tests
2020-05-22 14:36:01 +02:00
Arnar Kári Ágústsson
6ac2f4b74d
With reason relay example ( #12080 )
...
* Add with-reason-relay example
* update gitignore
* Add missing components
* Add _app.js wrapper
* Move records to wait for results
* Update readme
* Upload schema
* Add call to query hook to get viewerData with getFragmentRefs
* Move relay env setup to seperate module
* remove unused code
* lint fixes
* prettier fix
2020-05-22 12:13:44 +02:00