archive/rsnext
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
17106 commits 5 branches 0 tags 1.9 GiB
Commit graph

34 commits

Author SHA1 Message Date
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
Artyom Kurnikov
fe3f520d8d
Update Fauna example with new guestbook (#27295) 
Based on https://github.com/vercel/next.js/pull/26708

- Renames FaunaDB -> Fauna
- Moves to Tailwind instead of bespoke styling
- Use SWR instead of hand-rolled fetch wrapper
- List/Create API for Guestbook
- Preps for setting correct environment variables from Vercel integration
 2021-08-02 17:09:04 +00:00
Luc Leray
f52955ec94
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 19:58:03 +00:00
Nick Babcock
5629223407
Update examples to use React 17 (#26133) 
[With next 11 requiring react 17](https://nextjs.org/blog/next-11#upgrade-guide), most of the examples
need to be updated, so the following snippet updated all the examples to
a compatible react version.

```bash
cd examples/
fd -g 'package.json' | xargs sed -r -i 's/"react": ".*"/"react": "^17.0.2"/
fd -g 'package.json' | xargs sed -r -i 's/"react-dom": ".*"/"react-dom": "^17.0.2"/'

# exclude experimental react version
git checkout with-reason-relay/package.json
```
 2021-06-16 16:43:26 +00:00
Tim Neutkens
de08b1fff1
Remove unsupported examples (#26075) 
Co-authored-by: JJ Kasper <jj@jjsweb.site>
 2021-06-14 20:27:06 +02:00
Lee Robinson
279e105279
Update .now.sh to .vercel.app. (#22359) 2021-04-14 09:46:06 -05: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
Josh
51f2a530d6
Updated deploy button URL (#20756) 
* Updated deploy button URL

* Update bottom button
 2021-01-05 17:36:33 -05:00
Allen Hai
2b817af1ea
Update fauna example (#19806) 
This PR removes the `next.config.js` file with an `env` key and instead modifies the setup script to create a `.env.local` file with the provided credentials. 

I also made some changes to the Deploy Button to ask for the environment variables when creating a new project.
 2020-12-04 01:28:37 +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
Riccardo Di Maio
bdaedd220a
Remove another broken demo link from with-graphql-faunadb (#16007) 
The link used to appear twice in the README, but it has only been removed once (#15267) to fix #15219. This commit removes the other link to the broken demo.
 2020-08-08 17:05:29 +00:00
Luis Alvarez D
a475480745
[Examples] Remove broken demo from with-graphql-faunadb (#15267) 
Fixes https://github.com/vercel/next.js/issues/15219

This is better than replacing the demo as having a demo could allow users to post any kind of comments that we can't control.
 2020-07-17 16:44:32 +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
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
b7e17e09e5
Update references to zeit/next.js (#13463) 2020-05-27 17:51:11 -04:00
JJ Kasper
1f6ce106ae
Update codeload and deploy links for org rename (#13141) 
Co-authored-by: Joe Haddad <joe.haddad@zeit.co>
 2020-05-27 14:11:39 -04:00
Joe Haddad
dbad9db68c
Update Examples for Fast Refresh (#13068) 2020-05-18 17:44:18 -04:00
Joe Haddad
86160a5190
Upgrade to Prettier 2 (#13061) 2020-05-18 15:24:37 -04:00
Tim Neutkens
483bd3ddda
Rename ZEIT to Vercel (#12075) 
* Find/replace

* Update more URLs

* More rename

* Fix remaining examples

* More updates

* Update create-next-app

* Update remaining text

* Update

Co-authored-by: Shu Uesugi <shu@chibicode.com>
 2020-04-21 11:47:12 +02:00
Shu Uesugi
c57cdbb31d
Rename zeit.co/new → zeit.co/import (#10674) 
* Replace zeit.co/new → zeit.co/import

* Update deployment.md
 2020-02-24 19:08:34 -05:00
Gordey
5e23e35456
Add missin create permission for faunadb example (#10575) 2020-02-18 10:24:57 -05:00
Shu Uesugi
5f041447bc
Remove Now CLI reference from examples (#10501) 
* Find/Replace "Deploy it to the cloud..."

* Find/Replace "Deploy it to the cloud..." (no colon)

* Find/Replace "Deploy it to the cloud..." for firebase

* Convert remaining ones

* Storybook deployment

* Update with-stripe-typescript

* Update contributing.md

* Remove `now`

* Update examples/with-stripe-typescript/README.md

Co-Authored-By: Luis Alvarez D. <luis@zeit.co>
 2020-02-12 17:14:57 -05:00
Abhishek Warokar
372031246d Fix typo in FaunaDB example (#10304) 
Colleciton -> Collection
 2020-01-28 16:30:16 +01:00
Matthew Sweeney
b0053a4a73 Update FaunaDB Example Instructions (#10280) 
* update fauna example instructions

* change key name in setup script
 2020-01-27 12:52:04 +01:00
fauna-brecht
7d419f885e Let users define their own database as easily as possible. (#10209) 
* Let users define their own client token.

* Make sure users know that GraphQL schema can also be done via the UI

* Update README.md

* Update setup.js

Co-authored-by: Matthew Sweeney <mail@msweeneydev.com>
Co-authored-by: Joe Haddad <timer150@gmail.com>
 2020-01-22 15:16:56 -05:00
Shu Uesugi
6804039e94 Make example READMEs more consistent (#10124) 
* npx create → npm init

* Fix inconsistent instructions

* Update amp-first

* Update with-graphql-react

* with-firebase-cloud-messaging

* Update with-higher-order-component

* change create-next-app url

* Update create-next-app instruction

* Update instructions to use npm instead of npx

* Move "the idea behind the example" to top

* Rename

* Rename

* Update contributing.md with a README template
 2020-01-16 23:23:56 +01:00
Luis Alvarez D
7edf0da0c4 Add the deploy button to compatible examples (#9547) 2019-11-27 11:40:58 -05:00
Luis Alvarez D
8e2097997e
Remove getInitialProps from the faunadb example (#9427) 
* Remove the global fetch

* Update API methods

* Remove getInitialProps from the page

* Add client side fetching
 2019-11-15 13:21:08 -05:00
Joe Haddad
34a38d2e40
Linting should be strict (#9418) 
This configures our linting to exit without a success status code when warnings are found
 2019-11-14 23:01:36 -08:00
Luis Alvarez D
f910a92f18
Updated readme (#9405) 2019-11-13 16:26:08 -05:00
fauna-brecht
581e338614 with-graphql-faunadb (#9387) 
* with-graphql-faunadb

* Use latest next

* Use node-fetch

* removed import to next/config

* Updated titles

* Lint fix

* Link to the schema
 2019-11-13 13:15:27 -05:00