Skip to content

/ next.js

The React Framework

nextjs.org
MIT License
65k stars 11.8k forks
Star
Notifications
canary
Switch branches/tags
7 branches 1,101 tags
Go to file
Code
Clone

Use Git or checkout with SVN using the web URL.

Latest commit

@timneutkens
timneutkens v10.1.1
2 cd46241 Mar 29, 2021
v10.1.1
cd46241 2

Git stats

Files

Permalink
Failed to load latest commit information.
Type
Name
Latest commit message
Commit time
.github
Add PR template
Mar 19, 2021
.vscode
Check if parentspan is provided in profiler (#22061)
Feb 12, 2021
bench
whitespace flag enabled</a>. - OpenTelemetry is replaced with a custom and lightweight tracing solution. - Three trace targets are currently supported: console, Zipkin, and NextJS. - Tracing is now governed by environment variables rather than `--require instrument.js`. + `TRACE_TARGET`: one of `CONSOLE`, `ZIPKIN`, or `TELEMETRY`; defaults to `TELEMETRY` if unset or invalid. + `TRACE_ID`: an 8-byte hex-encoded value used as the Zipkin trace ID; if not provided, this value will be randomly generated and passed down to subprocesses. Other sundry: - I'm missing something, probably a setup step, with the Zipkin target. Traces are captured successfully, but you have to manually enter the Trace ID in order to view the trace - it doesn't show up in queries. - I'm generally unhappy with [this commit](https://github.com/vercel/next.js/pull/22713/commits/235cedcb3ead76b630b4c8aa695f904489da2831). It is... untidy to provide a telemetry object via `setGlobal`, but I don't have a ready alternative. Is `distDir` strictly required when creating a new Telemetry object? I didn't dig too deep here. As noted, there are a lot of changes, so it'd be great if a reviewer could: - [ ] pull down the branch and try to break it - [ ] check the Zipkin traces and identify possible regressions in the functionality Closes #22570 Fixes #22574" class="Link--secondary" href="next.js/commit/e27b7e996d6e7e6772272f3d189ce93dac25fc3d.html">Telemetry-compatible tracing (#22713whitespace flag enabled</a>. - OpenTelemetry is replaced with a custom and lightweight tracing solution. - Three trace targets are currently supported: console, Zipkin, and NextJS. - Tracing is now governed by environment variables rather than `--require instrument.js`. + `TRACE_TARGET`: one of `CONSOLE`, `ZIPKIN`, or `TELEMETRY`; defaults to `TELEMETRY` if unset or invalid. + `TRACE_ID`: an 8-byte hex-encoded value used as the Zipkin trace ID; if not provided, this value will be randomly generated and passed down to subprocesses. Other sundry: - I'm missing something, probably a setup step, with the Zipkin target. Traces are captured successfully, but you have to manually enter the Trace ID in order to view the trace - it doesn't show up in queries. - I'm generally unhappy with [this commit](https://github.com/vercel/next.js/pull/22713/commits/235cedcb3ead76b630b4c8aa695f904489da2831). It is... untidy to provide a telemetry object via `setGlobal`, but I don't have a ready alternative. Is `distDir` strictly required when creating a new Telemetry object? I didn't dig too deep here. As noted, there are a lot of changes, so it'd be great if a reviewer could: - [ ] pull down the branch and try to break it - [ ] check the Zipkin traces and identify possible regressions in the functionality Closes #22570 Fixes #22574" class="Link--secondary" href="next.js/commit/e27b7e996d6e7e6772272f3d189ce93dac25fc3d.html">)
Mar 10, 2021
docs
Fix YAML parsing issue in ESLint docs. (#23511)
Mar 29, 2021
errors
Update webpack5.md
Mar 29, 2021
examples
Update `with-docker` example and deployment docs. (#23486)
Mar 28, 2021
packages
v10.1.1
Mar 29, 2021
test
Make eslint opt-in until it lands on stable (#23509)
Mar 29, 2021
.eslintignore
Add ESLint to Next.js (#22437)
Mar 23, 2021
.eslintrc.json
Remove unused variable (#13716)
Jun 3, 2020
.gitignore
Ignore emacs lockfiles (#20497)
Dec 29, 2020
.npmrc
Remove version prefix
Oct 1, 2018
.prettierignore
feat: webpack inlining with configuration for v4 / v5 (#20598)
Jan 14, 2021
.prettierignore_staged
feat: webpack inlining with configuration for v4 / v5 (#20598)
Jan 14, 2021
.prettierrc.json
Prettier `trailingComma` default value to `es5` since 2.0 (#14391)
Jun 22, 2020
CODE_OF_CONDUCT.md
Update Code of Conduct email address (#12108)
Apr 22, 2020
SECURITY.md
Create SECURITY.md
Jul 13, 2020
UPGRADING.md
Move upgrading guide to /docs (#10727)
Feb 28, 2020
azure-pipelines.yml
Add pr section to azure config (#20758)
Jan 5, 2021
check-examples.sh
Ensure all examples are MIT licensed (#16691)
Aug 30, 2020
check-pre-compiled.sh
feat: webpack inlining with configuration for v4 / v5 (#20598)
Jan 14, 2021
contributing.md
Consistent use of colons in contributing docs (#23260)
Mar 22, 2021
jest.config.js
Upgrade jest-worker (#23077)
Mar 16, 2021
lerna.json
v10.1.1
Mar 29, 2021
license.md
Update license year for all packages
Jan 11, 2021
lint-staged.config.js
Update browserslist/caniuse-lite (#13605)
May 31, 2020
package.json
Upgrade jest-worker (#23077)
Mar 16, 2021
publish-release.sh
Make sure to exit publish script with correct code (#10310)
Jan 28, 2020
readme.md
Monorepo (#5341)
Sep 30, 2018
release-stats.sh
Update release stats workflow (#17580)
Oct 5, 2020
release.js
Remove common PR title prefixes
Aug 7, 2020
run-tests.js
Upgrade jest-worker (#23077)
Mar 16, 2021
skip-docs-change.js
Update CI docs change diff check (#21558)
Jan 26, 2021
test-file.txt
Add additional file serving tests (#12479)
May 4, 2020
test-pnp.sh
Add ESLint to Next.js (#22437)
Mar 23, 2021
vercel.json
Silence GH Comments for Preview URLs (#18766)
Nov 3, 2020
yarn.lock
Add os-browserify dep (#23354)
Mar 29, 2021
Next.js Getting Started Documentation Who is using Next.js? Community Contributing Authors

readme.md

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.

Authors

About

The React Framework

nextjs.org

Topics

react blog static-site-generator components node browser compiler tooling universal nextjs static toolbox server-rendering hybrid static-site-generation ssg vercel

Resources

Readme

License

MIT License

Releases 1,101

v10.1.1 Latest
Mar 29, 2021
+ 1,100 releases

Packages

No packages published

Used by 246k

  • @jdm-0126
  • @neilpalima
  • @starpro123
  • @Hamed-kshiem
  • @hitnei
  • @xEHLE
  • @sharmaankit25
+ 246,122

Contributors 1,539

+ 1,528 contributors

Languages