No description
Find a file
Maia Teegarden a784d54ab5
Fix/upload binary artifact (#29069)
* Fix upload of binary artifacts

* Build next-swc binaries

Co-authored-by: kodiakhq[bot] <49736102+kodiakhq[bot]@users.noreply.github.com>
2021-09-13 16:40:06 -07:00
.github Fix/upload binary artifact (#29069) 2021-09-13 16:40:06 -07:00
.vscode Improve jaeger traces (#28168) 2021-08-17 09:18:47 +02:00
bench Make traces in development reliable (#28990) 2021-09-13 15:49:29 +02:00
docs Add note about using Sharp for next/image to deployment docs. (#29067) 2021-09-13 20:31:04 +00:00
errors Throw error if res is accessed after gSSP returns (#29010) 2021-09-13 17:10:46 -05:00
examples [Examples] Updates with-google-tag-manager example to use <Script> component (#29061) 2021-09-13 17:43:35 +00:00
packages Fix/upload binary artifact (#29069) 2021-09-13 16:40:06 -07:00
scripts exclude test files from copy in trace-next-server (#28819) 2021-09-06 13:14:10 +02:00
test Throw error if res is accessed after gSSP returns (#29010) 2021-09-13 17:10:46 -05:00
.alexignore Enable Alex documentation linting for docs (#26598) 2021-06-25 11:40:50 -05:00
.alexrc Enable Alex documentation linting for docs (#26598) 2021-06-25 11:40:50 -05:00
.eslintignore Make traces in development reliable (#28990) 2021-09-13 15:49:29 +02:00
.eslintrc.json [ESLint] Remove error when file patterns are unmatched + ESLint setup changes (#27119) 2021-07-16 20:19:08 +02:00
.gitignore Add initial next swc package with first transform (#27355) 2021-07-27 17:07:28 +02:00
.npmrc Remove version prefix 2018-10-02 01:35:56 +02:00
.prettierignore chore: Set Prettier to ignore test output (#26353) 2021-07-20 14:37:44 -05:00
.prettierignore_staged feat: webpack inlining with configuration for v4 / v5 (#20598) 2021-01-13 20:59:08 -05:00
.prettierrc.json Prettier trailingComma default value to es5 since 2.0 (#14391) 2020-06-22 13:25:24 +02:00
azure-pipelines.yml Update test set-up to leverage playwright when able to (#28634) 2021-09-13 14:36:25 +02:00
CODE_OF_CONDUCT.md Update Code of Conduct email address (#12108) 2020-04-22 16:27:24 +02:00
contributing.md Update test set-up to leverage playwright when able to (#28634) 2021-09-13 14:36:25 +02:00
jest.config.js Update test set-up to leverage playwright when able to (#28634) 2021-09-13 14:36:25 +02:00
lerna.json v11.1.3-canary.15 2021-09-10 11:20:55 +02:00
license.md Update license year for all packages 2021-01-11 11:12:19 +01:00
lint-staged.config.js Replace CLIEngine with ESLint (#25801) 2021-06-09 13:54:10 +02:00
package.json Make traces in development reliable (#28990) 2021-09-13 15:49:29 +02:00
readme.md Monorepo (#5341) 2018-10-01 01:02:10 +02:00
release.js Match last PR mention in commit message for release notes 2021-05-07 19:53:38 +02:00
run-tests.js Update test set-up to leverage playwright when able to (#28634) 2021-09-13 14:36:25 +02:00
SECURITY.md Create SECURITY.md 2020-07-13 19:25:08 +02:00
skip-docs-change.js Update repo scripts to separate folder (#26787) 2021-07-01 13:41:27 +02:00
test-file.txt Add additional file serving tests (#12479) 2020-05-04 11:58:19 -05:00
tsconfig.json Update test set-up to leverage playwright when able to (#28634) 2021-09-13 14:36:25 +02: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
yarn.lock Make traces in development reliable (#28990) 2021-09-13 15:49:29 +02: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 which have a relatively limited scope. This is a great place to get started, gain experience, and get familiar with our contribution process.

Authors