- 15 Jan, 2021 4 commits
-
-
Joe Haddad authored
-
Gerald Monaco authored
-
Gerald Monaco authored
* Upgrade React version warning * Fix font/stylesheet plugin * Fix size-limit tests * Fix build-output test * Add tests for React 16 * Fix react-dom version
-
Guy Bedford authored
This picks up on the inlining work in https://github.com/vercel/next.js/pull/20598 to also include webpack loader inlining optimizations. This includes: * The dependencies of sass-loader * resolve-url-loader And for added benefit: * babel-plugin-transform-define * babel-plugin-transform-react-remove-prop-types style-loader and css-loader didn't inline easily. Perhaps we can come back to these ones.
-
- 14 Jan, 2021 6 commits
-
-
Lee Robinson authored
-
Joe Haddad authored
-
Ramiro Silveyra d'Avila authored
Co-authored-by:Joe Haddad <joe.haddad@zeit.co>
-
François Billioud authored
Rookie mistake
😉 -
Ludovico Fischer authored
Get rid of the unmet peer dependency warning when installing a next.js project wtih node-sass 5. node-sass 5 is the currently maintained version and removes support one deprecated API and Node.js versions that Next.js does not support either. Next.js uses node-sass 5 in devDependencies. node-sass changelog: https://github.com/sass/node-sass/releases On the other hand, as the docs encourage the sass package instead of node-sass, (see errors/duplicate-sass.md) I have updated examples which used node-sass 4 to the latest sass instead.
-
Guy Bedford authored
-
- 13 Jan, 2021 7 commits
-
-
kaykdm authored
Fixes: https://github.com/vercel/next.js/issues/19100 > According to https://nextjs.org/docs/basic-features/image-optimization#caching Next.js populates a cache dir when using the new <Image /> component. This is not the case when using SVG files. This results in a performance penalty. I created a function for writing images to cache directory (`wrirteToCacheDir`) and it is called for all images. However, vector and animated images are not optimized before writing them to cache dir Related to #18179
-
Ari Freyr Asgeirsson authored
Hello friends Ran into this bug on our production site, prerenderManifest stores revalidation info for the index as `"/": { .. }`, but the code tries to access this information as `"/index"`. This leads to our index page always having s-max-age: 1 -
Janicklas Ralph authored
-
JJ Kasper authored
This ensures the page has transitioned fully before testing which should resolve the random failure seen in a couple of runs. x-ref: https://github.com/vercel/next.js/pull/20918#issuecomment-758155230
-
Volodymyr Klymenko authored
Co-authored-by:kodiakhq[bot] <49736102+kodiakhq[bot]@users.noreply.github.com>
-
Lalit authored
Update link from https://swr.now.sh to https://swr.vercel.app
-
Lee Robinson authored
From https://github.com/vercel/next.js/discussions/20992.
-
- 12 Jan, 2021 2 commits
-
-
Baheya Khalifa authored
-
Lee Robinson authored
Please let me know if anything is missing from this document
😄
-
- 11 Jan, 2021 20 commits
-
-
JJ Kasper authored
This helps catch conflicting paths returned from `getStaticPaths` with a friendly error <details> <summary> Preview of error </summary> <img width="962" alt="Screen Shot 2021-01-08 at 5 03 04 PM" src="https://user-images.githubusercontent.com/22380829/104074719-6e481100-51d6-11eb-9397-938aee3ae30b.png"> <img width="962" alt="Screen Shot 2021-01-08 at 5 03 41 PM" src="https://user-images.githubusercontent.com/22380829/104074722-6f793e00-51d6-11eb-90f6-7cdf9882bf00.png"> </details> Closes: https://github.com/vercel/next.js/issues/19527
-
JJ Kasper authored
* Skip GitHub actions tests for irrelevant changes * add docs lint step * Add lint-no-typescript * Update docs lint * Skip at the job level * Update steps * remove un-needed dep * Update compare branch * log remotes * output to stderr * fetch origin * Update fetch * update diffing * Update command handling * test output * Update check * Log output * Update outputs * Add id for build job * Update output * Update precompiled * remove testing check
-
Joe Haddad authored
-
Joe Haddad authored
This pull request adds `future.strictPostcssConfiguration`, allowing users to opt-into the more strict PostCSS configuration loading. This stricter PostCSS configuration loading ensures that CSS can be cached across builds.
-
Spencer Elliott authored
-
Kristoffer K authored
**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`
-
Kristoffer K authored
**What's the problem this PR addresses?** In https://github.com/vercel/next.js/pull/18921 I enabled `absoluteRuntime` for everyone (it was only enabled for PnP users) but didn't consider that people used the babel preset outside of the webpack build. Fixes https://github.com/vercel/next.js/issues/19448 - ~~Since it doesn't contain a repro I can't be certain but based on feedback from @koshea in https://github.com/vercel/next.js/pull/18921#issuecomment-733744645 I'll assume @RossMcMillan92 is doing the same thing, because when next is building it doesn't leave absolute paths as external.~~ Confirmed in https://github.com/vercel/next.js/pull/18921#issuecomment-734224014 **How did you fix it?** Only enable `absoluteRuntime` when the preset is running under `babel-loader`
-
Ludovico Fischer authored
Fixes #20474 * Switch API url to working URL used in apollo example * Update deps * Move styled jsx out of the way to avoid demonstrating too many unfamiliar concepts at once dev, build and start work now.
-
Tim Neutkens authored
Fixes #20408 Fixes #20925
-
Vlad Frolov authored
I have not bumped into any bug, I was just playing around https://lgtm.com/projects/g/vercel/next.js/, and this looked like a legit suggestion to fix
-
Almad authored
Co-authored-by:Tim Neutkens <tim@timneutkens.nl>
-
Hyeon Kim (김지현) authored
Prevent unpredictable dependency hosting by explicitly resolve module path on webpack.ProvidePlugin (#20971) ProvidePlugin replaces certain identifiers with another modules. As a result, 'buffer' and 'process' modules are added as implicit dependencies to all Next.js plugins. This can be problematic. With "Plug'n'Play" strategy, it don't work at all since they fail-fast with implicit dependencies. With "node_modules" strategy, it might seem OK but actually it can be result into unpredictable behavior since in uses dependency [hoisting](https://yarnpkg.com/advanced/lexicon#hoisting). For example, currently users cannot use next-auth plugin with Plug'n'Play strategy:  This patch let Next.js properly handles such cases with `require.resolve`. Closes https://github.com/vercel/next.js/issues/20955 ###### References: - https://github.com/nextauthjs/next-auth/pull/1034
-
Lachlan Campbell authored
Co-authored-by:
Tim Neutkens <tim@timneutkens.nl> Co-authored-by:
Tim Neutkens <timneutkens@me.com>
-
Tim Neutkens authored
Fixes #20887
-
Tom authored
Co-authored-by:kodiakhq[bot] <49736102+kodiakhq[bot]@users.noreply.github.com>
-
Tom authored
-
taisei mima authored
-
Michael McQuade authored
-
Michael McQuade authored
-
Victor Assis authored
-
- 10 Jan, 2021 1 commit
-
-
Tim Neutkens authored
-