- 12 Jan, 2022 5 commits
-
-
Tim Neutkens authored
-
Tim Neutkens authored
-
Rich Haines authored
Co-authored-by:
Lee Robinson <me@leerob.io> Co-authored-by:
Balázs Orbán <info@balazsorban.com>
-
Hiroaki Ogasawara authored
* Docs: correct ignorance pattern for env.local In order to gitignore `.env.local`, I need to add `.env*.local` instead of `.env.*.local` to `.gitignore`. * Update docs/basic-features/environment-variables.md Co-authored-by:
Steven <steven@ceriously.com> * Update docs/basic-features/environment-variables.md Co-authored-by:
Balázs Orbán <info@balazsorban.com> Co-authored-by:
Steven <steven@ceriously.com> Co-authored-by:
Balázs Orbán <info@balazsorban.com>
-
Manny Becerra authored
* copy cleanup in env. variables docs * copy cleanup in fast refresh docs * Supplements #33153 - updating existing cross-references to `master` branch to renamed default branch of `main` * Supplements #33153 - updating existing cross-references to `master` branch to renamed default branch of `main` Co-authored-by:kodiakhq[bot] <49736102+kodiakhq[bot]@users.noreply.github.com>
-
- 11 Jan, 2022 5 commits
-
-
JJ Kasper authored
-
JJ Kasper authored
* JSON.stringify generic errors * Add util for normalizing errors * lint-fix * Add better error for null case as well Co-authored-by:Michael Ozeryansky <mozeryansky@users.noreply.github.com>
-
kaykdm authored
x-ref [#31552 ](https://github.com/vercel/next.js/issues/31552) x-ref https://github.com/vercel/next.js/issues/32115 x-ref https://github.com/vercel/next.js/issues/32546 x-ref https://github.com/vercel/next.js/issues/32721 Since this PR https://github.com/vercel/next.js/pull/31455 is merged, `enhanced-resolve` dependency's resolved field is changed which caused broken yarn pnp. I am not sure how this field has been changed or this is intentional or not When I install webpack locally, `enhanced-resolve`'s resolved field in lock file is always `registry.yarnpkg.com` not `codeload.github.com` ## Bug - [x] 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 - [ ] 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 - [ ] Make sure the linting passes by running `yarn lint` Co-authored-by:
Tobias Koppers <1365881+sokra@users.noreply.github.com> Co-authored-by:
JJ Kasper <22380829+ijjk@users.noreply.github.com>
-
Tobias Koppers authored
-
Fatih Kalifa authored
* next-swc: fix ssg code elimination when used in render * simplify logic and add more thorough tests * comment * remove fold_export_default and fix JSX member expression
-
- 10 Jan, 2022 7 commits
-
-
Glenn Gijsberts authored
## Desscription This is a follow up of https://github.com/vercel/next.js/pull/32873. As discussed in #32873, currently it's not recommended to use getServerSideProps in the `Error` component, so this PR will add that caveat to the documentation page, like `Document` and `App` also have. ## Documentation / Examples - [x] Make sure the linting passes by running `yarn lint`
-
JJ Kasper authored
-
Gal Schlezinger authored
After discussing with @sokra, seems that the proposed solution is split in two: * We need to make sure that the `process` polyfill uses `global.process` if available. This is because middlewares are bundled using `browser` target and therefore `process.env.MY_ENV` gets shimmed into `require('process').env.MY_ENV`. * Allow `process.env` to be statically analyzed for dependencies so they will be exported to the manifest. Related issues: * should fix #33043. -
Tobias Koppers authored
it should not leak into the client runtime cc @javivelasco ## 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 - [ ] 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 - [ ] Make sure the linting passes by running `yarn lint`
-
Alexandru Tenie authored
Proposes fix to #33110 Adds info on environment variables and the /src folder in the following docs: - https://nextjs.org/docs/advanced-features/src-directory - https://nextjs.org/docs/basic-features/environment-variables#loading-environment-variables ## 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 `yarn lint` Co-authored-by:
Tim Neutkens <6324199+timneutkens@users.noreply.github.com>
-
Manny Becerra authored
Proposes some minor text-copy cleanup in the following docs: - https://nextjs.org/docs/basic-features/fast-refresh - https://nextjs.org/docs/basic-features/environment-variables ## 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 `yarn lint`
-
Donny/강동윤 authored
-
- 08 Jan, 2022 1 commit
-
-
David Babel authored
## Feature We are in a Typescript context, but the `next.config.js` cannot be parsed as is, since it fails on `File is a CommonJS module; it may be converted to an ES module.ts(80001)` so it does not parse the rest of the file :  Here we should have an error because the type is not the expected one. With a little trick, it's possible to enable the check by : - adding `// @ts-check` at first line - moving the export at the end of the file And then it works like a charm :  Co-authored-by:
JJ Kasper <22380829+ijjk@users.noreply.github.com>
-
- 07 Jan, 2022 1 commit
-
-
David Fateh authored
This PR accomplishes 2 things: 1. You can now add images to the rich text post of the example and see those images show up in the app. This is a good jumping off point for people who are learning how to customize the rich text renderers by adding custom components to the mapper. 2. Updating the README pictures to have a more up-to-date UI in the screenshots. ## Feature - [x] Documentation added ## Documentation / Examples - [x] Make sure the linting passes by running `yarn lint`
-
- 06 Jan, 2022 7 commits
-
-
Balázs Orbán authored
-
JJ Kasper authored
-
Simon Kirsten authored
Fixes [a small bug](https://github.com/vercel/next.js/pull/32967#issuecomment-1006277236) that caused the build to crash if a _middleware is present at the root of the project and standalone mode is enabled.
-
JJ Kasper authored
* Add util for generating new tests/error documents * update compiled * lint-fix * apply suggestions * update wording * update compiled
-
JJ Kasper authored
Removes extra config per https://github.com/vercel/next.js/pull/32808/files#r779282629 ## Documentation / Examples - [x] Make sure the linting passes by running `yarn lint`
-
Lee Robinson authored
The relative path was not working.
-
Steven authored
This bumps `@vercel/nft` to the latest version and consequently bumps `graceful-fs` to the latest version. - Fixes #33003 - Related to https://github.com/vercel/nft/pull/258 - Related to https://github.com/browserify/resolve/issues/264Co-authored-by:
JJ Kasper <22380829+ijjk@users.noreply.github.com>
-
- 05 Jan, 2022 12 commits
-
-
Lee Robinson authored
Building off https://github.com/vercel/next.js/pull/31465 for `next export` docs. - Clearly explains the standard output from `next build` - Move Dockerfile snippet to example, instead of embedded directly - Clarify both Vercel and `next start` use the Build API output spec - Less emphasis on recommending Vercel (more neutrality) - Mention Middleware & Edge Functions when discussing Vercel - Add "Going to Production" link at the bottom for related reading
-
JJ Kasper authored
-
Balázs Orbán authored
Something [between `11.0.2-canary.5` and `11.0.2-canary.6`](https://github.com/vercel/next.js/compare/v11.0.2-canary.5...v11.0.2-canary.6) changed the behavior that logged any runtime errors in `getStaticProps` to stderr. This is only observable if `getStaticProps` has a `revalidate` value, and the build did not fail. The error has to happen in a subsequent revalidation step. This PR reverts the change and fixes #30375. ## Bug - [x] Related issues linked using `fixes #number` - [x] 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 - [ ] 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 - [ ] Make sure the linting passes by running `yarn lint` Co-authored-by:
JJ Kasper <22380829+ijjk@users.noreply.github.com>
-
David Brookton authored
## `with-next-translate` Example Refactor - [x] Linting passes ## Purpose for changes - The existing locals folder is using a redundant string structure which continuously repeats "Change language to " in separate instances in separate languages alongside separate language translations. - This PR is a simple refactor to extract "change language to" to it's own string, and references already existing strings defining the language translation. ## Why they might be helpful - A user looking to implement this pattern should consider reducing redundancies as early as possible to scale an app, thus I believe it would be helpful for this example. Notes: - these original translations were done via google translate - verified that these strings still make sense and translate properly in every locale / language - these strings are meant to be examples, translations have not been verified with a translation agency. Co-authored-by:JJ Kasper <22380829+ijjk@users.noreply.github.com>
-
Rohith Gilla authored
## 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 - [ ] 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 `yarn lint`
-
Vicente Soriano authored
## Documentation / Examples - [x] Make sure the linting passes by running `yarn lint` Closes: https://github.com/vercel/next.js/pull/32023 Fixes: https://github.com/vercel/next.js/issues/32015
-
Teo Stocco authored
> Based on https://github.com/vercel/next.js/blob/v12.0.1/packages/next/server/render.tsx#L522-L532, this avoids the need for double page render. After investigation, the potential unneeded render has been introduced in the official [example](https://github.com/vercel/next.js/pull/20228/files#diff-3976da223aaf15067ecdd0734ca277ebf4629c46d62f89d732ab392752d3572dR6) but does not exist in the earlier proposed [solution](https://gist.github.com/colinhacks/c40519a6a050a99091862319151377ec). There might a reason (layered override?) for it but I am unable to find relevant explanation. Original discussion in https://github.com/mantinedev/mantine/pull/348. ## Documentation / Examples - [x] Make sure the linting passes by running `yarn lint`
-
Kumar Deepanshu authored
## 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 - [ ] 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 - [ ] Make sure the linting passes by running `yarn lint`
-
Guillaume FORTAINE authored
## 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 - [ ] 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 - [ ] Make sure the linting passes by running `yarn lint`
-
JJ Kasper authored
-
Hung Viet Nguyen authored
Co-authored-by:JJ Kasper <jj@jjsweb.site>
-
Jared Palmer authored
-
- 04 Jan, 2022 2 commits
-
-
JJ Kasper authored
-
JJ Kasper authored
* Fix build-native jobs * Update to latest turbo * fix extra space * fix windows shell * Update to latest turbo * Bump Turbo (#32703) * Bump turbo to canary * Bump turbo * Update yaml too * add less specific restore key * update more restore keys * Fix non-unique key and cache wasm build * ensure turbo is installed for new jobs * remove old wasm cache * update directory check * bump * re-add if publish checks Co-authored-by:Jared Palmer <jared@jaredpalmer.com>
-