- 02 Oct, 2022 6 commits
-
-
Tim Neutkens authored
-
Bartosz Kaszubowski authored
# Why Use the custom, build-in logger for the dev server messages, to unify their appearance with other ones: <img width="415" alt="Screenshot 2022-10-02 135927" src="https://user-images.githubusercontent.com/719641/193454207-88c415a2-9b43-45f3-ae52-3f088bccfd01.png"> # How Replace `console` with `Log` calls in `next-dev-server.ts`.
-
JJ Kasper authored
This adds a proper error when we detect conflicting app and page paths. Fixes: https://vercel.slack.com/archives/C043ANYDB24/p1664678172389449 ## Bug - [x] Related issues linked using `fixes #number` - [x] Integration tests added - [ ] Errors have a helpful link attached, see `contributing.md` Co-authored-by:
Sukka <isukkaw@gmail.com>
-
Tim Neutkens authored
Co-authored-by:Balázs Orbán <info@balazsorban.com>
-
JJ Kasper authored
x-ref: [slack thread](https://vercel.slack.com/archives/CGU8HUTUH/p1664579732577999) x-ref: https://github.com/vercel/next.js/actions/runs/3162459138/jobs/5149086901 x-ref: https://github.com/vercel/next.js/actions/runs/3162459138/jobs/5149086956 Also fixes invalid example env file name breaking checkout on Windows x-ref: https://dev.azure.com/nextjs/next.js/_build/results?buildId=41449&view=logs&jobId=59111904-15f9-56fe-00af-da61f595b979 ## Bug - [x] Related issues linked using `fixes #number` - [ ] Integration tests added - [ ] Errors have a helpful link attached, see `contributing.md`
-
Paulo Augusto Silva authored
The docs have a misleading `console.log` output for the input `process.env` that doesn't display all the variables on edge runtime. The example shows an output of a supposed object with all the environment variables, but it does this when logging a specific variable. ## Documentation / Examples - [ ] Make sure the linting passes by running `pnpm lint` - [ ] The "examples guidelines" are followed from [our contributing doc](https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md)
-
- 01 Oct, 2022 18 commits
-
-
Balázs Orbán authored
-
Balázs Orbán authored
Applies https://github.com/vercel/next.js/pull/38214#pullrequestreview-1126083066 ## Bug - [ ] Related issues linked using `fixes #number` - [ ] Integration tests added - [ ] Errors have a helpful link attached, see `contributing.md` ## Feature - [ ] Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. - [ ] Related issues linked using `fixes #number` - [ ] Integration tests added - [ ] Documentation added - [ ] Telemetry added. In case of a feature if it's used or not. - [ ] Errors have a helpful link attached, see `contributing.md` ## Documentation / Examples - [ ] Make sure the linting passes by running `pnpm lint` - [ ] The "examples guidelines" are followed from [our contributing doc](https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md)
-
Eliaz Bobadilla authored
easier to read ## Documentation / Examples - [x ] Make sure the linting passes by running `pnpm lint` - [ x] The "examples guidelines" are followed from [our contributing doc](https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md) Co-authored-by:
Balázs Orbán <18369201+balazsorban44@users.noreply.github.com>
-
Balázs Orbán authored
-
Balázs Orbán authored
-
Balázs Orbán authored
-
Balázs Orbán authored
Lands #39289 with code suggestions to comply with our [example guideliens](https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md) closes #39289 ## Bug - [ ] Related issues linked using `fixes #number` - [ ] Integration tests added - [ ] Errors have a helpful link attached, see `contributing.md` ## Feature - [ ] Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. - [ ] Related issues linked using `fixes #number` - [ ] Integration tests added - [ ] Documentation added - [ ] Telemetry added. In case of a feature if it's used or not. - [ ] Errors have a helpful link attached, see `contributing.md` ## Documentation / Examples - [ ] Make sure the linting passes by running `pnpm lint` - [ ] The "examples guidelines" are followed from [our contributing doc](https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md) Co-authored-by:
Patrik Szewczyk <patrik.szewczyk@gmail.com>
-
Balázs Orbán authored
-
Gebov authored
This is an example of how to integrate [Sitefinity CMS ](https://www.progress.com/sitefinity-cms)with next.js Co-authored-by:
Balázs Orbán <info@balazsorban.com>
-
Freddy Montes authored
<!-- Thanks for opening a PR! Your contribution is much appreciated. In order to make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change that you're making: --> This adds a new example under cms-dotcms/. Is a general-purpose example that should allow developers to undestand how to use next.js with dotCMS apis. ## Bug - [ ] Related issues linked using `fixes #number` - [ ] Integration tests added - [ ] Errors have helpful link attached, see `contributing.md` ## Feature - [ ] Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. - [ ] Related issues linked using `fixes #number` - [ ] Integration tests added - [x] Documentation added - [ ] Telemetry added. In case of a feature if it's used or not. - [ ] Errors have helpful link attached, see `contributing.md` ## Documentation / Examples - [x] Make sure the linting passes by running `pnpm lint` - [x] The examples guidelines are followed from [our contributing doc](https://github.com/vercel/next.js/blob/canary/contributing.md#adding-examples) Co-authored-by:
Daniel Esteves <estevesd8@gmail.com> Co-authored-by:
Will Ezell <will@dotcms.com> Co-authored-by:
Arcadio Quintero A <oidacra@gmail.com> Co-authored-by:
Rafael <rjvelazco21@gmail.com>
-
rodrigo authored
### Example - Moved to typescript - Making use of the Image API (old example only use image tag) ### Dependencies - updated deps to latest - removed unused deps, just to focus on the current example and not other ones ``` @material-ui/core, @material-ui/icons, jss, mobile-detect, react-jss ``` ### Deploy [Example deploy](https://rmcexample-86mr9qpaa-falsepopsky.vercel.app/) ## Documentation / Examples - [x] Make sure the linting passes by running `pnpm lint` - [x] The examples guidelines are followed from [our contributing doc](https://github.com/vercel/next.js/blob/canary/contributing.md#adding-examples) Co-authored-by:
Balázs Orbán <info@balazsorban.com>
-
Balázs Orbán authored
-
Balázs Orbán authored
-
Balázs Orbán authored
Lands #38163 with merge conflict fixes. Needed to open a new PR, because GitHub does not allow maintainers to edit organization forks. https://github.com/orgs/community/discussions/5634 Closes #38163 ## Bug - [ ] Related issues linked using `fixes #number` - [ ] Integration tests added - [ ] Errors have a helpful link attached, see `contributing.md` ## Feature - [ ] Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. - [ ] Related issues linked using `fixes #number` - [ ] Integration tests added - [ ] Documentation added - [ ] Telemetry added. In case of a feature if it's used or not. - [ ] Errors have a helpful link attached, see `contributing.md` ## Documentation / Examples - [ ] Make sure the linting passes by running `pnpm lint` - [ ] The "examples guidelines" are followed from [our contributing doc](https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md) Co-authored-by:
sherazmalik06 <sherazmalik06@gmail.com> Co-authored-by:
Tony Spiro <tspiro@tonyspiro.com>
-
Balázs Orbán authored
Lands #39048 with lint fixes. Needed to open a new PR, because GitHub does not allow maintainers to edit organization forks. https://github.com/orgs/community/discussions/5634 Closes #39048 ## Bug - [ ] Related issues linked using `fixes #number` - [ ] Integration tests added - [ ] Errors have a helpful link attached, see `contributing.md` ## Feature - [ ] Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. - [ ] Related issues linked using `fixes #number` - [ ] Integration tests added - [ ] Documentation added - [ ] Telemetry added. In case of a feature if it's used or not. - [ ] Errors have a helpful link attached, see `contributing.md` ## Documentation / Examples - [ ] Make sure the linting passes by running `pnpm lint` - [ ] The "examples guidelines" are followed from [our contributing doc](https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md) Co-authored-by:
Chris Fisher <chris.i.fisher@gmail.com>
-
sic!kh authored
Added examples to `getStaticProps` & `getServerSideProps` explicit and implicit typings for TypeScript. Related issues: fixes https://github.com/vercel/next.js/issues/40607Co-authored-by:
Balázs Orbán <18369201+balazsorban44@users.noreply.github.com>
-
Angelo Ashmore authored
## Documentation / Examples - [ ] Make sure the linting passes by running `pnpm lint` - [x] The examples guidelines are followed from [our contributing doc](https://github.com/vercel/next.js/blob/canary/contributing.md#adding-examples) **Note**: `pnpm lint` fails on code unrelated to the changes in this PR. This PR updates the [Prismic](https://prismic.io/) CMS example (`examples/cms-prismic`) to use the latest Prismic libraries, tools, and conventions. - Uses `npx @slicemachine/init` to bootstrap new Prismic accounts and content repositories. - Uses [Slice Machine](https://prismic.io/docs/technologies/slice-machine) to model content. - Uses [Slices](https://prismic.io/docs/technologies/slice) to write post content. - Uses the latest versions of the following packages: - `@prismicio/client` - `@prismicio/helpers` - `@prismicio/react` - `@prismicio/next` - Adds generated TypeScript types for Prismic content. The example remains as a JavaScript codebase (i.e. not TypeScript), but makes use of the types via JSDoc. Co-authored-by:
Balázs Orbán <info@balazsorban.com>
-
JJ Kasper authored
Fixes: https://vercel.slack.com/archives/C03KAR5DCKC/p1664581332858249 ## Bug - [x] Related issues linked using `fixes #number` - [ ] Integration tests added - [ ] Errors have a helpful link attached, see `contributing.md`
-
- 30 Sep, 2022 16 commits
-
-
Jiachi Liu authored
Follow up for #40132 Do not apply pages lint rule `@next/next/no-html-link-for-pages` for appDir
-
sanruiz authored
Fixing the image URL in the meta property og:image <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change that you're making: --> ## Documentation / Examples - [x] Make sure the linting passes by running `pnpm lint` - [x] The "examples guidelines" are followed from [our contributing doc](https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md)
-
OJ Kwon authored
<!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change that you're making: --> This PR utilizes cargo's new feature from latest release (1.64.0), inheriting dependency from a workspace. In short, top-level workspace cargo manifest can specify a version of dependency to use, then actual packages uses it without re-declaring version per each via workspace = true. This will help to dedupe different versions of packages, also potentially avoid conflicts if forgot to bump up specific versions. In this pr only touches swc_core, which is a base dependency we use in several place. One another benefit for this is bump up PR can be lot more simplified, only need to update single Cargo.toml when we bump up. Note rust-toolchain has updated to use nightly version after 1.64.0 to enable this. ## Bug - [ ] Related issues linked using `fixes #number` - [ ] Integration tests added - [ ] Errors have a helpful link attached, see `contributing.md` ## Feature - [ ] Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. - [ ] Related issues linked using `fixes #number` - [ ] Integration tests added - [ ] Documentation added - [ ] Telemetry added. In case of a feature if it's used or not. - [ ] Errors have a helpful link attached, see `contributing.md` ## Documentation / Examples - [ ] Make sure the linting passes by running `pnpm lint` - [ ] The "examples guidelines" are followed from [our contributing doc](https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md)
-
Henrik Wenz authored
## Changes see commits ## Additional Info Since this example is quite complex I tried to remove additional noise (unused type inference). ## Documentation / Examples - [x] Make sure the linting passes by running `pnpm lint` - [x] The "examples guidelines" are followed from [our contributing doc](https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md) ## Related Closes: #40975
-
Hannes Bornö authored
Stringify into one json object instead. Previously parsing would break if a string included a semicolon. ## Bug - [ ] Related issues linked using `fixes #number` - [ ] Integration tests added - [ ] Errors have a helpful link attached, see `contributing.md` ## Feature - [ ] Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. - [ ] Related issues linked using `fixes #number` - [ ] Integration tests added - [ ] Documentation added - [ ] Telemetry added. In case of a feature if it's used or not. - [ ] Errors have a helpful link attached, see `contributing.md` ## Documentation / Examples - [ ] Make sure the linting passes by running `pnpm lint` - [ ] The "examples guidelines" are followed from [our contributing doc](https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md)
-
Hannes Bornö authored
Fixes local weight type which could break if you wrote "regular" instead of 400. Adds `variable` property to google font loader to let you define the name of the CSS variable. ## Bug - [ ] Related issues linked using `fixes #number` - [ ] Integration tests added - [ ] Errors have a helpful link attached, see `contributing.md` ## Feature - [ ] Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. - [ ] Related issues linked using `fixes #number` - [ ] Integration tests added - [ ] Documentation added - [ ] Telemetry added. In case of a feature if it's used or not. - [ ] Errors have a helpful link attached, see `contributing.md` ## Documentation / Examples - [ ] Make sure the linting passes by running `pnpm lint` - [ ] The "examples guidelines" are followed from [our contributing doc](https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md)
-
Shu Ding authored
Currently, we use the `isClient ? 'deterministic' : 'named'` condition for module IDs. We did that because in the context of server compiler, the server graph (RSC) can directly know the module ID of the referenced module in the client graph (SSR). The client module's ID _is_ the module reference module's resource path. However, that makes the server bundle and the manifest file larger because these module IDs cannot be minified. In this PR we are changing it to `deterministic`, with another mapping for server SSR. ## Bug - [ ] Related issues linked using `fixes #number` - [ ] Integration tests added - [ ] Errors have a helpful link attached, see `contributing.md` ## Feature - [ ] Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. - [ ] Related issues linked using `fixes #number` - [ ] Integration tests added - [ ] Documentation added - [ ] Telemetry added. In case of a feature if it's used or not. - [ ] Errors have a helpful link attached, see `contributing.md` ## Documentation / Examples - [ ] Make sure the linting passes by running `pnpm lint` - [ ] The "examples guidelines" are followed from [our contributing doc](https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md)
-
Lee Robinson authored
Reverts vercel/next.js#40016. `pageExtensions` is not frequently used – as is mostly a workaround until the Layouts RFC lands. Thus, it doesn't make sense to place a note on the Middleware page and expect readers to need to connect the dots and understand `pageExtensions`. Further, the example docs linked could be more specific about Middleware to prevent this confusion. I will also make that change here. Co-authored-by:Balázs Orbán <info@balazsorban.com>
-
Hannes Bornö authored
Finds the root layout segments for flight requests. If those segments doesn't match the FlightRouterState it's a new root layout and a full page reload is required. ## Bug - [ ] Related issues linked using `fixes #number` - [ ] Integration tests added - [ ] Errors have a helpful link attached, see `contributing.md` ## Feature - [ ] Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. - [ ] Related issues linked using `fixes #number` - [ ] Integration tests added - [ ] Documentation added - [ ] Telemetry added. In case of a feature if it's used or not. - [ ] Errors have a helpful link attached, see `contributing.md` ## Documentation / Examples - [ ] Make sure the linting passes by running `pnpm lint` - [ ] The "examples guidelines" are followed from [our contributing doc](https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md) Co-authored-by:
Tim Neutkens <6324199+timneutkens@users.noreply.github.com>
-
Balázs Orbán authored
Re-lands #40335 but without modifying the lock file. ## Bug - [ ] Related issues linked using `fixes #number` - [ ] Integration tests added - [ ] Errors have a helpful link attached, see `contributing.md` ## Feature - [ ] Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. - [ ] Related issues linked using `fixes #number` - [ ] Integration tests added - [ ] Documentation added - [ ] Telemetry added. In case of a feature if it's used or not. - [ ] Errors have a helpful link attached, see `contributing.md` ## Documentation / Examples - [ ] Make sure the linting passes by running `pnpm lint` - [ ] The "examples guidelines" are followed from [our contributing doc](https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md)
-
Jamie Barton authored
## Documentation / Examples - [x] Make sure the linting passes by running `pnpm lint` - [x] The "examples guidelines" are followed from [our contributing doc](https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md) This PR fixes the npm/pnpm/yarn commands to use with-xata instead of Contentful.
-
Saurabh Burade authored
## Documentation / Examples - [x] Make sure the linting passes by running `pnpm lint` - [x] The examples guidelines are followed from [our contributing doc](https://github.com/vercel/next.js/blob/canary/contributing.md#adding-examples) The template repository can be found [here](https://github.com/saurabhburade/with-evm-chains) Public reviews, and improvement suggestions are welcome! ## Supported Blockchains 1. ETHEREUM 2. ROPSTEN 3. RINKEBY 4. GÖRLI 5. KOVAN 6. MATIC 7. MATIC_TESTNET 8. FANTOM 9. FANTOM_TESTNET 10. XDAI 11. BSC 12. BSC_TESTNET 13. ARBITRUM 14. ARBITRUM_TESTNET 15. MOONBEAM_TESTNET 16. AVALANCHE and more ### Note - This template has the flexibility to seamlessly extend to other EVM Blockchains. - It has web3.js and wallet connection modules. - It supports blockchain Read and Write functionalities. Co-authored-by:
Balázs Orbán <18369201+balazsorban44@users.noreply.github.com>
-
John Carlo Austria authored
## Bug - [ ] Related issues linked using `fixes #number` - [ ] Integration tests added - [ ] Errors have a helpful link attached, see `contributing.md` ## Feature - [ ] Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. - [ ] Related issues linked using `fixes #number` - [ ] Integration tests added - [ ] Documentation added - [ ] Telemetry added. In case of a feature if it's used or not. - [ ] Errors have a helpful link attached, see `contributing.md` ## Documentation / Examples - [ ] Make sure the linting passes by running `pnpm lint` - [ ] The "examples guidelines" are followed from [our contributing doc](https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md) Response to #29165 Co-authored-by:
Balázs Orbán <18369201+balazsorban44@users.noreply.github.com>
-
Tim Neutkens authored
-
Tim Neutkens authored
-
Tim Neutkens authored
This reverts commit 24f573f8.
-