No description
Find a file
Maia Teegarden 4df6804c5a
Add Web Tooling team to codeowners (#43981)
<!--
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 that you're making:
-->

## Bug

- [ ] Related issues linked using `fixes #number`
- [ ] Integration tests added
- [ ] Errors have a helpful link attached, see
[`contributing.md`](https://github.com/vercel/next.js/blob/canary/contributing.md)

## Feature

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

## Documentation / Examples

- [ ] Make sure the linting passes by running `pnpm build && pnpm lint`
- [ ] The "examples guidelines" are followed from [our contributing
doc](https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md)
2022-12-12 14:06:49 -06:00
.devcontainer Add support for next.js development in docker (#43138) 2022-11-23 11:35:49 +01:00
.github Add Web Tooling team to codeowners (#43981) 2022-12-12 14:06:49 -06:00
.husky Replace pre-commit with husky (#38350) 2022-07-06 11:14:16 -05:00
.vscode Add VSCode settings and recommended extensions for Next.js repository (#43954) 2022-12-12 15:10:54 +01:00
bench BREAKING CHANGE: Remove React 17 (#41629) 2022-10-21 22:20:36 +00:00
contributing Clarify e2e dependency on yarn in contributin docs (#43287) 2022-12-09 12:34:32 +00:00
docs Update compiler.md (#43872) 2022-12-10 15:38:43 +00:00
errors Add helpful error for createContext used in Server Components (#43747) 2022-12-11 20:46:29 -06:00
examples corrected /examples/github-pages readme (#43766) 2022-12-12 02:33:38 +00:00
packages next-dev: restart dev server exceeds the memory limits (#43958) 2022-12-12 18:54:55 +00:00
scripts Apply publish step optimizations (#43620) 2022-12-01 21:48:51 -08:00
test Open server component errors fullscreen (#43887) 2022-12-12 12:27:06 +00:00
.alexignore Enable Alex documentation linting for docs (#26598) 2021-06-25 11:40:50 -05:00
.alexrc Add section to next/future/image docs about Known Browser Bugs (#39759) 2022-08-20 00:21:00 +00:00
.eslintignore Improve RSC plugin to provide better errors (#42435) 2022-11-23 17:26:38 -08:00
.eslintrc.json Hybrid App Hooks Support (#41767) 2022-10-31 20:13:27 -07:00
.gitattributes the way towards webpack 5 typings (#29105) 2021-09-21 19:17:16 +02:00
.gitignore Fix next/dynamic types for resolving named export module (#43923) 2022-12-10 17:35:13 +00:00
.npmrc declare pnpm7 as engine (#37303) 2022-05-30 13:13:36 +00:00
.prettierignore chore: check against npm version in issue validator (#38915) 2022-08-25 11:43:20 -05:00
.prettierignore_staged Fix typo pnpm-lock.yam in .prettierignore_staged (#42212) 2022-10-30 22:58:45 -07:00
.prettierrc.json Prettier trailingComma default value to es5 since 2.0 (#14391) 2020-06-22 13:25:24 +02:00
azure-pipelines.yml Align pnpm version (#41123) 2022-10-03 17:07:52 +02:00
CODE_OF_CONDUCT.md updated code of conduct to v2.1 (#34208) 2022-02-10 18:11:42 -06:00
contributing.md refactor: split up CONTRIBUTING.md (#40515) 2022-09-16 14:54:58 -07:00
jest.config.js Mock @next/font when using next/jest (#42413) 2022-11-03 11:12:46 -07:00
jest.replay.config.js Add Replay integration for dev e2e tests (#40955) 2022-09-29 14:45:10 -07:00
lerna.json v13.0.7-canary.4 2022-12-09 09:04:30 -06:00
license.md Update license year 2022-01-13 16:02:34 +01:00
lint-staged.config.js Replace pre-commit with husky (#38350) 2022-07-06 11:14:16 -05:00
package.json Upgrade playwright to 1.28.1 (#43818) 2022-12-07 14:14:55 -08:00
plopfile.js refactor: split up CONTRIBUTING.md (#40515) 2022-09-16 14:54:58 -07:00
pnpm-lock.yaml v13.0.7-canary.4 2022-12-09 09:04:30 -06:00
pnpm-workspace.yaml misc: add benchmarking script for edge rendering (#40716) 2022-09-27 17:57:16 +02:00
readme.md Monorepo (#5341) 2018-10-01 01:02:10 +02:00
release.js Fix labels for release sections 2021-11-21 13:11:54 +01:00
run-tests.js Fix test retry cleanup (#43011) 2022-11-16 13:16:35 -08:00
test-file.txt Add additional file serving tests (#12479) 2020-05-04 11:58:19 -05:00
tsconfig-tsec.json Integrate tsec into the linting process (#33746) 2022-02-24 16:59:18 -08:00
tsconfig.json Adds tests to ensure eslint-plugin-next's available rules are properly exported and recommended rules are correctly defined. (#38183) 2022-06-30 11:31:33 -05:00
tsec-exemptions.json Fix various Trusted Types violations without use of policy (#34726) 2022-05-05 00:11:36 +00:00
turbo.json Update caching for swc turbo builds (#42929) 2022-11-15 08:24:04 -08:00
UPGRADING.md Move upgrading guide to /docs (#10727) 2020-02-28 23:46:18 +01:00
vercel.json Silence GH Comments for Preview URLs (#18766) 2020-11-03 21:59:47 +00:00

Next.js

Getting Started

Visit https://nextjs.org/learn to get started with Next.js.

Documentation

Visit https://nextjs.org/docs to view the full documentation.

Who is using Next.js?

Next.js is used by the world's leading companies. Check out the Next.js Showcase to learn more.

Community

The Next.js community can be found on GitHub Discussions, where you can ask questions, voice ideas, and share your projects.

To chat with other community members you can join the Next.js Discord.

Our Code of Conduct applies to all Next.js community channels.

Contributing

Please see our contributing.md.

Good First Issues

We have a list of good first issues that contain bugs that have a relatively limited scope. This is a great place to get started, gain experience, and get familiar with our contribution process.

Authors

Security

If you believe you have found a security vulnerability in Next.js, we encourage you to responsibly disclose this and not open a public issue. We will investigate all legitimate reports. Email security@vercel.com to disclose any security vulnerabilities.

https://vercel.com/security