No description
c2dfe40296
@timneutkens it'd be great to get your input. These changes introduce a new Babel loader that eliminates much of the existing overhead, resulting in better HMR speeds. Multithreading is still in flight, and may be omitted if speed improvements end up being negligible. For now, the new loader is hidden behind an `experimental` flag. Items to be completed before this PR is ready to merge: - [x] reconfigure `ncc` to precompile the parts of `@babel/core` and `@babel/traverse` that we're accessing directly - [x] change `@babel/core/...` imports to `ncc`ed version - [x] ~~measure multithreading (not currently pushed) functionality, and include the functionality depending on the results~~ I'll open a separate PR for this - [x] ensure TypeScript is happy with all imports as final step (`--no-verify` was used to bypass) There will be two follow-up PRs: - loader support for projects with custom `.babelrc` - multithreaded loader (should the change we warranted after measurement) |
||
---|---|---|
.github | ||
.vscode | ||
bench | ||
docs | ||
errors | ||
examples | ||
packages | ||
test | ||
.eslintignore | ||
.eslintrc.json | ||
.gitignore | ||
.npmrc | ||
.prettierignore | ||
.prettierignore_staged | ||
.prettierrc.json | ||
azure-pipelines.yml | ||
check-examples.sh | ||
check-pre-compiled.sh | ||
CODE_OF_CONDUCT.md | ||
contributing.md | ||
jest.config.js | ||
lerna.json | ||
license.md | ||
lint-staged.config.js | ||
package.json | ||
publish-release.sh | ||
readme.md | ||
release-stats.sh | ||
release.js | ||
run-tests.js | ||
SECURITY.md | ||
skip-docs-change.js | ||
test-file.txt | ||
test-pnp.sh | ||
UPGRADING.md | ||
vercel.json | ||
yarn.lock |
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
- Tim Neutkens (@timneutkens) – Vercel
- Naoyuki Kanezawa (@nkzawa) – Vercel
- Guillermo Rauch (@rauchg) – Vercel
- Arunoda Susiripala (@arunoda)
- Tony Kovanen (@tonykovanen)
- Dan Zajdband (@impronunciable)