archive/rsnext
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
No description
7666 commits 5 branches 0 tags 1.9 GiB
JavaScript 81.6%
TypeScript 15.3%
Rust 2.3%
MDX 0.4%
CSS 0.4%
Find a file
Kristoffer K 1c75bf789b
perf(next): use require.resolve instead of resolve (#19518) 
**What's the problem this PR addresses?**

- ~~https://github.com/vercel/next.js/pull/18768 started to ncc babel and thus it's version of resolve which breaks PnP support~~
Babel replaced `resolve` with the builtin `require.resolve` and a polyfill for older node versions in https://github.com/babel/babel/pull/12439 which was upgraded in https://github.com/vercel/next.js/pull/20586
- `next` unnecessarily bundles the `resolve` package when `require.resolve` is builtin and can do the same job

**How did you fix it?**

- ~~Avoid running `resolve` through ncc~~
Added a test for https://github.com/vercel/next.js/issues/19334 (closes https://github.com/vercel/next.js/issues/19334)
- Replace `resolve` with `require.resolve`
2021-01-11 14:43:08 +00:00
.github fix(next): add missing peer dependencies for sass support (#17606) 2021-01-04 10:30:46 -05:00
.vscode Add profiling to webpack loaders (#20392) 2020-12-29 21:21:35 +00:00
bench Update profiling approach to cover webpack runs (#20900) 2021-01-09 20:12:13 -05:00
docs Add note on destructuring to Env Variables docs (#20869) 2021-01-11 11:13:24 +01:00
errors Error when exporting to static directory (#20969) 2021-01-11 13:34:58 +00:00
examples fix(examples): make with-graphql-hooks run correctly again (#20929) 2021-01-11 13:55:18 +00:00
packages perf(next): use require.resolve instead of resolve (#19518) 2021-01-11 14:43:08 +00:00
test Error when exporting to static directory (#20969) 2021-01-11 13:34:58 +00:00
.eslintignore Update Azure config (#18931) 2020-11-09 00:56:39 -05:00
.eslintrc.json Remove unused variable (#13716) 2020-06-03 11:58:58 -04:00
.gitignore Ignore emacs lockfiles (#20497) 2020-12-29 16:12:36 +00:00
.npmrc Remove version prefix 2018-10-02 01:35:56 +02:00
.prettierignore Update Azure config (#18931) 2020-11-09 00:56:39 -05:00
.prettierignore_staged Move next-codemod to Next.js monorepo (#15536) 2020-08-10 11:14:53 +02:00
.prettierrc.json Prettier trailingComma default value to es5 since 2.0 (#14391) 2020-06-22 13:25:24 +02:00
azure-pipelines.yml Add pr section to azure config (#20758) 2021-01-05 01:41:42 +00:00
check-examples.sh Ensure all examples are MIT licensed (#16691) 2020-08-29 22:32:35 -04:00
check-pre-compiled.sh Pre-ncc compiled packages to prevent re-nccing unnecessarily (#11569) 2020-04-07 09:42:16 -04:00
CODE_OF_CONDUCT.md Update Code of Conduct email address (#12108) 2020-04-22 16:27:24 +02:00
contributing.md Fix deploy buttons URLs (#20834) 2021-01-07 01:40:29 +00:00
jest.config.js Use the jest-circus test runner (#12974) 2020-05-16 16:56:06 -04:00
lerna.json v10.0.5 2021-01-06 18:30:00 -05:00
license.md Update license year for all packages 2021-01-11 11:12:19 +01:00
lint-staged.config.js Update browserslist/caniuse-lite (#13605) 2020-05-31 19:37:01 +00:00
package.json deps: upgrade various deps (mainly babel) (#20586) 2020-12-29 20:10:08 +00:00
publish-release.sh Make sure to exit publish script with correct code (#10310) 2020-01-28 14:03:32 -05:00
readme.md Monorepo (#5341) 2018-10-01 01:02:10 +02:00
release-stats.sh Update release stats workflow (#17580) 2020-10-05 09:32:12 +00:00
release.js Remove common PR title prefixes 2020-08-07 09:34:50 +02:00
run-tests.js Fix failing Azure tests (#19877) 2020-12-08 09:24:22 +00:00
SECURITY.md Create SECURITY.md 2020-07-13 19:25:08 +02:00
test-file.txt Add additional file serving tests (#12479) 2020-05-04 11:58:19 -05:00
test-pnp.sh perf(next): use require.resolve instead of resolve (#19518) 2021-01-11 14:43:08 +00: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 perf(next): use require.resolve instead of resolve (#19518) 2021-01-11 14:43:08 +00:00

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