- 10 9月, 2020 3 次提交
-
-
由 Joe Haddad 提交于
Fixes #10142 Fixes #11629
-
由 Henrik Wenz 提交于
## Changelog - Updated slate.js to version 0.58.4 - Removed unused packages (immutable & slate-plain-serializer) - Simplified example (we don’t need to demonstrate the multi editor case anymore, since this issue is now handled by slate internally) - Remove deprecated `KeyUtils` - Removed deprecated Components ## Related: - https://github.com/ianstormtaylor/slate/issues/870
-
由 Borek Bernard 提交于
As the example is about Yarn workspaces, it should gitignore `.next` recursively.
-
- 09 9月, 2020 5 次提交
-
-
由 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
-
由 Sashank Thupukari 提交于
s/applicale/applicable/
-
由 Turcan Vladimir 提交于
-
由 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 4 次提交
-
-
由 Tim Neutkens 提交于
-
由 JJ Kasper 提交于
Co-authored-by: NTim Neutkens <timneutkens@me.com>
-
-
由 Luis Alvarez D 提交于
Closes https://github.com/vercel/next.js/issues/16633 - The docs and examples that use `as` have been updated to show how `href` can be used to get the same results - Added new examples and provided more details on current examples for more details on how `href` can be used. **Note:** With this change the usage of `as` becomes completely unrequired as I failed to find a good use case for it. Therefore documentation for `as` now includes: `Used for dynamic routes before Next.js 9.5.3`. But that should link to somewhere, either to a blog post or to the Upgrade Guide in our docs.
-
- 07 9月, 2020 5 次提交
-
-
由 Tim Neutkens 提交于
-
由 JJ Kasper 提交于
Co-authored-by: Nkodiakhq[bot] <49736102+kodiakhq[bot]@users.noreply.github.com>
-
由 Anders Kjær Damgaard 提交于
The BirdsPage name seems to have been copy/pasted from `pages/birds.js` and forgotten by mistake.
-
由 Tim Neutkens 提交于
-
由 JJ Kasper 提交于
-
- 06 9月, 2020 6 次提交
-
-
由 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
-
由 Mohsen Azimi 提交于
Is this switch necessary
-
由 Luis Alvarez D 提交于
Goals of this PR: - Explain `import()` first without mentioning `next/dynamic`, because `next/dynamic` in our API and **Dynamic Import** is a ES feature. This should avoid a common confusion in our users thinking that one can't be used without the other. - Mention how `next/dynamic` can be used with **Dynamic Imports** to load react components. - Updated example to include fuzzy search using a dynamic import. Potential change: Leave the page to be about `import()` and move `next/dynamic` to the API reference (alongside `next/link`, `next/router`, etc.) Closes https://github.com/vercel/next.js/pull/16299 Closes https://github.com/vercel/next.js/issues/15711
-
由 Adityo Pratomo 提交于
While running the current [auth0 example](https://github.com/vercel/next.js/tree/canary/examples/auth0), I bumped into this error while trying to access an API route from a page. ``` { "error": "_lib_auth0__WEBPACK_IMPORTED_MODULE_1__.default.tokenCache is not a function" } ``` After checking the [nextjs-auth0](https://github.com/auth0/nextjs-auth0) repo, I realize that they're using version 0.8.0 of the SDK. Changing the package.json to the appropriate version fixes this error. Signed-off-by: NAdityo Pratomo <pratomo.adityo@gmail.com>
-
由 Eugene C 提交于
Adding an example with [cssed](https://github.com/okotoki/cssed). A custom styling solution, which extracts CSS from template literals into separate files.
-
由 Kristoffer K 提交于
**What's the problem this PR addresses?** A decent amount of the examples don't have a `name` field in `package.json` that matches their folder name, meaning they either lack a name or the names are duplicated. I was testing Yarn 2 workspaces using the entire examples directory and needed to get rid of the duplicates. **How did you fix it?** Updated the names to match the names of their folders
-
- 05 9月, 2020 3 次提交
-
-
由 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
-
由 Shu Uesugi 提交于
Updating `with-google-analytics` example to be in line with [our documentation recommending `useRouter`](https://nextjs.org/docs/api-reference/next/router#userouter). Verified that it works.
-
- 04 9月, 2020 8 次提交
-
-
由 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
-
由 Peng Jie 提交于
Thanks vercel team create multiple examples for much use cases, I found some error messages and fixed it.
-
-
由 Zack Tanner 提交于
Fixes a warning being logged to the console when using `href` with a dynamic path. Fixes #16794
-
由 Jan Potoms 提交于
Alternative to https://github.com/vercel/next.js/pull/16798
-
由 Pedro Duarte 提交于
Hi
👋 [Stitches](https://stitches.dev) `v0.0.1` beta was recently released. This PR updates the existing examples to the latest packages and API. Notes: - Remove `with-stitches-styled` example, that's no longer needed - Update `with-stitches` example - Update dependency - Example done with Typescript - Updated README Thanks✌ ️ ![CleanShot 2020-09-03 at 18 23 09@2x](https://user-images.githubusercontent.com/372831/92141867-52d98d80-ee13-11ea-91ed-001cd46989f1.jpg) -
由 Gianmarco 提交于
-
- 03 9月, 2020 5 次提交
-
-
由 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
-
由 Ting-Hsiang Hsu 提交于
* fix(with-react-relay-network-modern): fix README.md typo error * fix(with-react-relay-network-modern): should not use store cache for create environment * fix(with-react-relay-network-modern): should not request api again * feat(with-react-relay-network-modern): add relay-hooks package * feat(with-react-relay-network-modern): use new RelayEnvironmentProvider * feat(with-react-relay-network-modern): add useQuery hook * fix(with-react-relay-network-modern): fix cache error * fix(with-react-relay-network-modern): fix server loading Co-authored-by: NLuis Alvarez <luis@vercel.com> Co-authored-by: Nkodiakhq[bot] <49736102+kodiakhq[bot]@users.noreply.github.com>
-
由 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 1 次提交
-
-
由 John Doe 提交于
* Create _document.js Includes the lang attribute with current language inside the <html> tag. * Lint fix Co-authored-by: NLuis Alvarez D <luis@vercel.com> Co-authored-by: Nkodiakhq[bot] <49736102+kodiakhq[bot]@users.noreply.github.com>
-