- 12 9月, 2020 2 次提交
-
-
由 Joe Haddad 提交于
-
由 Bogdan Chadkin 提交于
Ref https://github.com/webpack-contrib/terser-webpack-plugin/blob/v4.1.0/package.json#L44 cacache is a dependency of terser-webpack-plugin. The latest version depends on cacache 15 while next adds cacache 13. This may give unexpected results. Better keep it in sync with terser plugin.
-
- 11 9月, 2020 7 次提交
-
-
由 Bogdan Chadkin 提交于
Babel-preset-env includes includes optional chaining and nullish-coalescing since [7.8.0](https://github.com/babel/babel/releases/tag/v7.8.0). In this diff I removed these plugins from next preset to prevent dependency duplication when their newer versions are out.
-
由 Bogdan Chadkin 提交于
The new version replaced big clone-deep package with dependency-free klona - https://github.com/webpack-contrib/sass-loader/releases/tag/v10.0.0 - https://github.com/webpack-contrib/sass-loader/releases/tag/v9.0.0 Also deduped some related transitives.
-
由 Sakito Mukai 提交于
There was a security update for node-fetch. > This is an important security release. It is strongly recommended to update as soon as possible. https://github.com/node-fetch/node-fetch/blob/master/docs/CHANGELOG.md#v261
-
由 Joe Haddad 提交于
-
由 JJ Kasper 提交于
This adds an error when interpolation fails to make sure invalid `href`s aren't accidentally used and an invalid URL is built. Closes: https://github.com/vercel/next.js/issues/16944
-
由 Joe Haddad 提交于
-
由 Joe Haddad 提交于
-
- 10 9月, 2020 5 次提交
-
-
-
由 Joe Haddad 提交于
-
由 JJ Kasper 提交于
This makes sure we properly resolve a rewrite when only the `href` value is used. This was causing a full-reload and was missed in the existing test since we weren't making sure a full navigation didn't occur which has been added in this PR. Fixes: https://github.com/vercel/next.js/issues/16974
-
由 Joe Haddad 提交于
-
由 Joe Haddad 提交于
Fixes #10142 Fixes #11629
-
- 09 9月, 2020 3 次提交
-
-
由 Joe Haddad 提交于
-
由 Gerald Monaco 提交于
Removes `next-head-count`, improving support for 3rd party libraries that insert or append new elements to `<head>`. --- This is more or less what a solution with a `data-` attribute would look like, except that instead of directly searching for elements with that attribute, we serialize the elements expected in `<head>` and then find them/assume ownership of them during initialization (in a manner similar to React's reconciliation) based on their properties. There are two main assumptions here: 1. Content is served with compression, so duplicate serialization of e.g. inline script or style tags doesn't have a meaningful impact. Storing a hash would be a potential optimization. 2. 3rd party libraries primarily only insert new, unique elements to head. Libraries trying to actively manage elements that overlap with those that Next.js claims ownership of will still be unsupported. The reason for this roundabout approach is that I'd really like to avoid `data-` if possible, for maximum compatibility. Implicitly adding an attribute could be a breaking change for some class of tools or crawlers and makes it otherwise impossible to insert raw HTML into `<head>`. Adding an unexpected attribute is why the original `class="next-head"` approach was problematic in the first place! That said, while I don't expect this to be more problematic than `next-head-count` (anything that would break in this new model also should have broken in the old model), if that does end up being the case, it might make sense to just bite the bullet. Fixes #11012 Closes #16707 --- cc @Timer @timneutkens
-
由 JJ Kasper 提交于
This makes sure to the page path is the expected version to trigger refreshing on the client and adds additional tests to make sure it is working properly with these page variants. Closes: https://github.com/vercel/next.js/issues/16938
-
- 08 9月, 2020 2 次提交
-
-
由 Tim Neutkens 提交于
-
由 JJ Kasper 提交于
Co-authored-by: NTim Neutkens <timneutkens@me.com>
-
- 07 9月, 2020 4 次提交
-
-
由 Tim Neutkens 提交于
-
由 JJ Kasper 提交于
Co-authored-by: Nkodiakhq[bot] <49736102+kodiakhq[bot]@users.noreply.github.com>
-
由 Tim Neutkens 提交于
-
由 JJ Kasper 提交于
-
- 06 9月, 2020 1 次提交
-
-
由 JJ Kasper 提交于
This makes sure to strip the trailing slash before attempting to resolve the `href` against pages/dynamic routes and adds tests ensuring the correct pages are resolved with `trailingSlash: true` enabled. Fixes: https://github.com/vercel/next.js/issues/16872
-
- 05 9月, 2020 2 次提交
-
-
由 Joe Haddad 提交于
-
由 JJ Kasper 提交于
This makes sure we only pass the as value's `pathname` instead of the full value so that we don't accidentally include `query` values while resolving the rewrites. This also adds tests to ensure the rewrites are resolved with the correct query values when only providing `href` and when manually mapping them with `href` and `as` Fixes: https://github.com/vercel/next.js/issues/16825
-
- 04 9月, 2020 3 次提交
-
-
由 JJ Kasper 提交于
-
由 JJ Kasper 提交于
This corrects detecting of invalid page config exports and adds additional test cases for non-invalid config import/exports Closes: https://github.com/vercel/next.js/issues/16775
-
由 Jan Potoms 提交于
Alternative to https://github.com/vercel/next.js/pull/16798
-
- 03 9月, 2020 4 次提交
-
-
由 JJ Kasper 提交于
This is a follow-up to https://github.com/vercel/next.js/pull/16744 which shows the build/activity indicator while the data is being re-fetched to let the user know the re-fetching is occurring Closes: https://github.com/vercel/next.js/issues/16790
-
由 Joe Haddad 提交于
-
由 JJ Kasper 提交于
This adds initial support for reloading the page when `getStaticProps`, `getStaticPaths`, or `getServerSideProps` were changed for a page by triggering a reload when the server output for a page has changed but the client output has not since these methods aren't included in the client output. Closes: https://github.com/vercel/next.js/issues/13949
-
由 JJ Kasper 提交于
This corrects/makes sure interpolating dynamic route values for `href` works correctly. This provides an alternative approach to building the `href` value with `next/link` so that you don't need to worry about encoding the params manually. Closes: https://github.com/vercel/next.js/issues/13473 Closes: https://github.com/vercel/next.js/issues/14959 Closes: https://github.com/vercel/next.js/issues/16771
-
- 02 9月, 2020 7 次提交
-
-
由 JJ Kasper 提交于
Since the error overlay could be dismissed before this is resolved we need to make sure the component is still mounted before updating the state.
-
由 Joe Haddad 提交于
-
由 Alex Castle 提交于
This is a small change to the image post-processor logic. When it's looking for images to preload, it will now ignore SVGs, as these are rarely the relevant images for LCP.
-
由 Joe Haddad 提交于
-
由 Joe Haddad 提交于
-
由 Joe Haddad 提交于
-
由 Joe Haddad 提交于
-