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)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
Max Proske
5dd4999b64
Convert many examples to TypeScript ( #41825 )
...
Strategized with @balazsorban44 to open one larger PR, with changes to individual examples as separate commits.
For each example, I researched how multiple realworld codebases use the featured technology with TypeScript, to thoughtfully convert them by hand - nothing automated whatsoever.
## Documentation / Examples
- [X] Make sure the linting passes by running `pnpm lint`
- [X] The "examples guidelines" are followed from [our contributing doc](https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md )
2022-10-26 20:28:55 +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
HaNdTriX
9018da11ca
Remove with-global-stylesheet example ( #4913 )
...
* Deprecate with-global-stylesheet example
Use @zeit/next-css instead
https://github.com/zeit/next-plugins/tree/master/packages/next-css
RELATED ISSUE: #4902
* Deprecate with-global-stylesheet-simple example
Use @zeit/next-css instead
https://github.com/zeit/next-plugins/tree/master/packages/next-css
RELATED ISSUE: #4902
2018-08-07 18:36:28 -07:00
Michael Herold
5b3578e58f
#4751 - Explicitly mention install when cloning examples ( #4758 )
...
Preferably this installation wouldn't be necessary, but in lieu of a fix...
#4751
2018-07-11 23:56:15 +02:00
yhirano55
8c5c2c23bb
Update babel-plugin-module-resolver version in with-global-stylesheet ( #4360 )
...
I found build error, so I've updated babel-plugin-module-resolver
2018-05-13 18:09:25 +02:00
James Hegedus
f2e56609cd
Examples: stabalise README format and create-next-app usage ( #4009 )
...
* Examples: clarify language around Yarn create & npx
* add missing READMEs and create-next-app usage
* suggest people tag jthegedus in firebase related issues
* add yarn alt instructions
* cerebraljs example readme & fixes
2018-04-03 14:19:05 +02:00
Tim Neutkens
ebf0c47c25
Upgrade standard.js ( #4064 )
...
* Upgrade standard.js
# Conflicts:
# yarn.lock
* Upgrade babel-eslint
2018-03-27 20:11:03 +02:00
James Hegedus
b1d8b839dd
Examples: use npx and yarn create to run create-next-app on examples ( #4002 )
...
* remove global npm install of create-next-app
* add npx to create-next-app command in examples
* add bash to shell snippets
* add yarn create to next-app command in examples
* fix READMEs named with lowercase
* change READMEs to use UPPERCASE
2018-03-14 09:09:46 +01:00
Yevhen Uzhva
73bf0ab162
[Fix] with-global-stylesheet example ( #3741 )
2018-02-09 09:29:10 +01:00
Tim Huff
31b8e7ed47
Indicate how to import fonts ( #3676 )
...
Got this fix from issue #2302 . Libraries like `font-awesome` are pretty common. Indicating how to get them to work should be indicated in the `README.md` (if not added to the example)
2018-02-05 10:43:43 +01:00
Tim Neutkens
24c1ac6ca9
Use canary for all example downloads ( #3411 )
2017-12-06 18:12:42 -08:00
Fouad Matin
2528779394
examples: add create-next-app ( #3377 )
...
* examples: add create-next-app
* fix with-typescript readme
2017-12-02 20:30:17 -08:00
Eric Redon
96f5bcbd57
Uplift with-global-stylesheet example ( #3076 )
...
* Fix with-global-stylesheet example by depending on React≥16
* Bump other dependencies of with-global-stylesheet example
2017-10-11 21:32:45 +02:00
Henrik
f14297dc80
Normalize example package.json files ( #2350 )
2017-06-23 10:46:44 +02:00
Paul Molluzzo
d08e027a8c
Add deploy now button to the top of all example READMEs ( #1763 )
...
* Add deploy now button to the top of all example READMEs
* Remove unnecessary whitespace changes
2017-04-22 14:51:51 +02:00
Orlin M Bozhinov
b46502f8f1
corrected css pre-processing #readme link ( #1709 )
2017-04-14 17:54:55 -03:00
Tim Neutkens
7f0591896a
Use latest version of Next for all examples ( #1597 )
...
* Use latest for all examples
* Update yarn.lock
2017-04-03 09:46:35 +05:30
Larry Lu
4fb7e4bc64
Fix typo ( #1380 )
...
port 300 -> 3000
2017-03-10 09:10:44 +01:00
Orlin M Bozhinov
563856f477
postcss-loader, postcss-easy-import, normalize.css and autoprefixer ( #1352 )
2017-03-05 07:48:37 -08:00
Orlin M Bozhinov
38cc82d0bc
With global stylesheet paths ( #1327 )
...
* with-global-stylesheet without relative paths and with node_modules
* a parenthetical remark about material-components-web not being part of the example
2017-03-02 08:37:58 -08:00
Fabien Le Frapper
22c22efc35
Fix missing dependencies ( #1232 )
...
Tried to pull & run this example, it failed, complaining about missing react & react-dom dependencies
2017-02-21 16:40:18 +01:00
Davide Bertola
19f1125520
add global stylesheet example ( #1016 )
...
* add global stylesheet example
* fix avoiding html-escape of stylesheets
* update readme
* remove .gitignore
2017-02-12 00:22:35 +01:00
