- 26 Jan, 2022 12 commits
-
-
JJ Kasper authored
-
JJ Kasper authored
-
MJ authored
There is a duplicate key, `testEnvironment` in one of the examples that are located in docs/testing.md. In my humble opinion, It is not good to have an error in examples. My suggestion is we have only one key and it is up to developers what options they have for the `testEnvironment`. ## Documentation / Examples - [x] Make sure the linting passes by running `yarn lint`
-
Jeff authored
1. fix details on how next handles security headers * note: check your HSTS at https://hstspreload.org * if your using headers in the config you need to add them below like  ## 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` Co-authored-by:
Steven <229881+styfle@users.noreply.github.com>
-
JJ Kasper authored
-
JJ Kasper authored
-
Karl Horky authored
The paths starting with slashes in the ESLint config examples are absolute, which are almost never the correct configuration for a project. Using a relative path is a much more common configuration, and leads to much less debugging why these examples don't work. ## 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`
-
Tim Neutkens authored
-
Terence Bezman authored
## Feature Implements feature requested in https://github.com/vercel/next.js/issues/30805. A few people including myself have been looking to use Relay with Next.JS and want to use the new Rust Compiler. This is my stab at an implementation. ### How it works? Finds all `graphql` tagged template experssions and replaces them with `require`s to the file generated by Relay. ### Where I need help - I've only worked with Rust a handful of times so I would appreciate any feedback on my use of language features. - Is there any performance overhead to many duplicate usages of `require`? I imagine there's a cache in place but I want to be sure. - I've added some unit tests & integration tests but I might be missing some use cases. Feel free to comment some use cases I'm not thinking about. - [x] Related issues linked using `fixes #number` - [x] Integration tests added - [ ] Documentation added - I haven't added any docs since this is an experimental API. ## Documentation / Examples You're expected to be running the Relay Compiler along side Next.JS when you're developing. This is pretty standard. I wouldn't expect people to have any problem with this. ### Usage In your `next.config.js` ```js module.exports = { experimental: { relay: { language: 'typescript', // or 'javascript` artifactDirectory: 'path/to/you/artifact/directory' // you can leave this undefined if you did not specify one in the `relay.json` } } } ``` Co-authored-by:
Tim Neutkens <6324199+timneutkens@users.noreply.github.com>
-
Shu Ding authored
(#31506 for context) This PR implements the minimum viable web server on top of the Next.js base server, and integrates it into our middleware (edge) SSR runtime to handle all the requests. This also addresses problems like missing dynamic routes support in our current handler. Note that this is the initial implementation with the assumption that the web server is running under minimal mode. Also later we can refactor the `__server_context` environment to properly passing the context via the constructor or methods.
-
Donny/강동윤 authored
This PR applies - https://github.com/swc-project/swc/pull/3367
-
Choz authored
This fixes the documentation for getServerSideProps and getStaticProps which mislead the defined type. Current screenshot taken from [nextjs doc](https://nextjs.org/docs/api-reference/data-fetching/get-server-side-props)  However, the declared type for these types are using union type which represents **any of the following** instead of **optional**. Declared types; [GetStaticPropsResult](https://github.com/vercel/next.js/blob/canary/packages/next/types/index.d.ts#L107)  [GetServerSidePropsResult](https://github.com/vercel/next.js/blob/canary/packages/next/types/index.d.ts#L160)  --- ### This PR updates the documentation for their return values; **Before**: The `...` function should return an object with the following **optional** properties: **After**: The `...` function should return object with **any one of the following** properties: --- ## 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 - [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:
Vadi Taslim <70912283+vaditaslim@users.noreply.github.com>
-
- 25 Jan, 2022 5 commits
-
-
JJ Kasper authored
-
Baoshuo Ren authored
-
11koukou authored
* Added 'rootEl' oprional property to next/Image component resembling 'root' option of the Intersection Observer API * changed 'rootEl' to 'lazyBoundary' and its type as well * added test, fixed initial root detection * Update test/integration/image-component/default/test/index.test.js Co-authored-by:
Steven <steven@ceriously.com> * prop names changed * added 'lazyroot' prop to the documentation * removed unused import * Apply suggestions from code review * Update docs with lazyRoot added in 12.0.9 Co-authored-by:
Steven <steven@ceriously.com>
-
Donny/강동윤 authored
This PR applies - https://github.com/swc-project/swc/pull/3360 Closes https://github.com/vercel/next.js/issues/33600
-
Katie Byers authored
Reading over this page, it wasn't immediately clear to me if these were headers which would get read off of the incoming request, or headers to be added to the outgoing response. ## Documentation / Examples - [X] Make sure the linting passes by running `yarn lint`
-
- 24 Jan, 2022 12 commits
-
-
JJ Kasper authored
-
JJ Kasper authored
* Update other instances of node-fetch * update compiled
-
JJ Kasper authored
-
Florentin / 珞辰 authored
## Documentation / Examples - [x] Make sure the linting passes by running `yarn lint` This PR adds the new official plugin for class sorting from Tailwind Labs to the Tailwind example. Rel: https://tailwindcss.com/blog/automatic-class-sorting-with-prettier
-
JJ Kasper authored
-
JJ Kasper authored
-
Lee Robinson authored
[See feedback here](https://github.com/vercel/next.js/discussions/19065#discussioncomment-2021147) for how we could improve clarity on these docs.
-
-
Lee Robinson authored
Make it clear that `geo` is not populated by the default Next.js server, and requires your hosting platform to integrate with a geolocation service to look up the location based on the request. If self-hosting, for example, this could be achieved with the [Google Geolocation API](https://developers.google.com/maps/documentation/geolocation/overview).
-
Lee Robinson authored
This fixes the deploy button, which wasn't working.
-
Jiachi Liu authored
-
Donny/강동윤 authored
This PR applies - https://github.com/swc-project/swc/pull/3344 Resolves https://github.com/vercel/next.js/discussions/30237#discussioncomment-2014245 - https://github.com/swc-project/swc/pull/3348 - https://github.com/swc-project/swc/pull/3352 This fixes `jsc.experimental.keepImportAssertions`.
-
- 23 Jan, 2022 3 commits
-
-
PØL1 authored
* Removed the s Removed the s of "This option was moved to the top level" was before: "this options was moved to the top level" * Update packages/next/server/config-shared.ts Co-authored-by:
JJ Kasper <jj@jjsweb.site> * Suggestion of @ijjk * lint-fix Co-authored-by:
JJ Kasper <jj@jjsweb.site>
-
Nicolas Bouvrette 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 - [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 Co-authored-by:Lee Robinson <9113740+leerob@users.noreply.github.com>
-
Luis Alvarez D authored
Minor change to remove duplicated route in the documentation manifest, this should change the title of https://nextjs.org/docs/basic-features/data-fetching/index from  To: `Data Fetching: Overview | Next.js`. That's because our routes reducer is matching the parent route which doesn't have a title.
-
- 22 Jan, 2022 1 commit
-
-
Steven authored
- Fixes https://github.com/vercel/next.js/issues/33294Co-authored-by:
JJ Kasper <22380829+ijjk@users.noreply.github.com>
-
- 21 Jan, 2022 7 commits
-
-
JJ Kasper authored
This fixes a case where optional catch-all route values aren't normalized to an array properly when the `index` value is passed. An additional test case has been added to prevent regressing on this. x-ref: [slack thread](https://vercel.slack.com/archives/CGU8HUTUH/p1642791113093400) ## Bug - [ ] Related issues linked using `fixes #number` - [x] Integration tests added - [ ] Errors have helpful link attached, see `contributing.md`
-
JJ Kasper authored
-
Sævar Berg authored
Upgrading from 12.0.0 to 12.0.8 results in `[dev] error - Error: To use middleware you must provide a `hostname` and `port` to the Next.js Server` and this requirement did not seem to be documented anywhere. Fixes #33450 which seems to have been erroneously closed. ## 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:JJ Kasper <22380829+ijjk@users.noreply.github.com>
-
Jiachi Liu authored
Use stable v5 of styled-jsx
-
JJ Kasper authored
-
Jiachi Liu authored
Subtask of #31506 * move `serverBuildDir` and getter function of `publicDir` to next-server as only used place * simplify `getMiddlewareInfo`, remove `distDir` and other params could be accessed from web server itself
-
Shu Ding authored
Related to #31506, this PR adds `getPrerenderManifest` and `getRoutesManifest` methods to provide manifest files to the base server. In the future, we can consider making these methods async, or provide necessary manifests from the very top. ## 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`
-