- 25 3月, 2021 4 次提交
-
-
由 JJ Kasper 提交于
Previously we special cased serverless builds and ran the client/server builds serially to allow the server build to load manifests produced in the client. To help with memory usage and for consistency this updates server mode to build in the same way. ## Bug - [ ] Related issues linked using `fixes #number` - [ ] Integration tests added ## 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. ## Documentation / Examples - [ ] Make sure the linting passes
-
由 Shu Ding 提交于
If the upstream MIME type isn't prefixed with `image/`, the endpoint should directly response with a 400 error. ## Bug - [x] Fixes #23312 - [x] Integration tests added ## 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. ## Documentation / Examples - [ ] Make sure the linting passes
-
由 JJ Kasper 提交于
-
由 JJ Kasper 提交于
This adds support for a `has` field to `rewrites`, `redirects`, and `headers` to allow matching against `header`, `cookie`, and `query` values. Documentation and additional tests for the feature is also added in this PR. Closes: https://github.com/vercel/next.js/issues/22345
-
- 24 3月, 2021 12 次提交
-
-
由 Pedro Duarte 提交于
Hey
👋 I realise neither I or you want to keep reviewing and merging these "Update Stitches" PRs So I'm setting it to the `latest`. Thanks (and sorry) ## Documentation / Examples - [x] Make sure the linting passes -
由 Tobias Koppers 提交于
fixes some bugs and improves performance ## Bug - [ ] Related issues linked using `fixes #number` - [ ] Integration tests added ## 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. ## Documentation / Examples - [ ] Make sure the linting passes
-
由 Tim Neutkens 提交于
-
由 Joe Haddad 提交于
Co-authored-by: NTim Neutkens <timneutkens@me.com> Co-authored-by: NTim Neutkens <tim@timneutkens.nl>
-
由 matamatanot 提交于
## Bug - [ ] Related issues linked using `fixes #number` - [ ] Integration tests added ## 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. ## Documentation / Examples - [ ] Make sure the linting passes
-
由 Pedro Duarte 提交于
Hey
👋 Just a quick update to the latest version of Stitches. Thanks! <3 ## Documentation / Examples - [x] Make sure the linting passes -
由 Shu Ding 提交于
This is a follow-up PR of #19052, where `visibility: inherit` was mistakenly added back. It was removed in #23278. ## Bug - [ ] Related issues linked using `fixes #number` - [ ] Integration tests added ## 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. ## Documentation / Examples - [ ] Make sure the linting passes
-
由 JJ Kasper 提交于
-
由 Houssein Djirdeh 提交于
For #22228 This PR: - Adds ESLint to toolchain - Included by default for builds (`next build`) - Can be enabled for development (`next dev`) - Custom formatter built for output - Adds appropriate tests - Adds two documentation pages
-
由 Tim Neutkens 提交于
Brings back the remaining Node.js module polyfills to not break existing apps upgrading from webpack 4 to webpack 5. Fixes #23169 ## Bug - [x] Related issues linked using `fixes #number` - [x] Integration tests added ## 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. ## Documentation / Examples - [ ] Make sure the linting passes
-
由 Lee Robinson 提交于
Closes https://github.com/vercel/next.js/issues/23299 to fix issues with NPM 7.
-
由 Bruno Crosier 提交于
The current `<Image />` component does not fallback gracefully when JavaScript is disabled in the client / browser. You can test this with the [official Next/Image example](https://csb-4k0kr-p8ya8f304.vercel.app/), by disabling JavaScript in the browser's DevTools. Video demo: https://streamable.com/frkvw9 This PR aims to fix this behaviour by using `<noscript></noscript>` tags to conditionally display a standard `<img>` element using the `props` passed to `<Image />` when JavaScript is disabled. For browser sessions where JavaScript is enabled, this will not cause an increase in network requests, so there should be no downside. One area where this PR is a bit "hacky" is that it uses a negative `margin-top` to counteract `sizerStyle.paddingTop`. From what I can tell, `sizerStyle.paddingTop` is generated on the server side, where we can not know ahead of time whether JavaScript is enabled in the browser - hence why I've opted for this solution. Fixes #19223 Fixes #21214
-
- 23 3月, 2021 6 次提交
-
-
由 Mohamed SADAT 提交于
Hello this PR is in order to update xstate to the lastest version and use the `createMachine` method instead of `Machine`. I also added the inspect mode in order to show how we could use into a next.js app. ## Documentation / Examples - [x] Make sure the linting passes
-
由 Tim Neutkens 提交于
-
由 Tim Neutkens 提交于
## Bug - [ ] Related issues linked using `fixes #number` - [ ] Integration tests added ## 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. ## Documentation / Examples - [x] Make sure the linting passes
-
由 Lee Robinson 提交于
-
由 Pedro Duarte 提交于
## Examples - [x] Make sure the linting passes This PR updates the `with-stitches` example to use the Beta `0.1.0` release.
-
由 Shu Ding 提交于
This PR removes the `visibility` style property change from next/image. It was previously added in #18195 to fix a bug that when no `src` is set, and that bug is not valid anymore as all images will always have `src` (and a fallback too). It also fixes the problem that screen readers ignore elements with `visibility: hidden`. Fixes #23201. ## Bug - [x] Related issues #23201 - [ ] Integration tests added ## 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. ## Documentation / Examples - [ ] Make sure the linting passes
-
- 22 3月, 2021 6 次提交
-
-
由 Johan Eliasson 提交于
Co-authored-by: Nkodiakhq[bot] <49736102+kodiakhq[bot]@users.noreply.github.com>
-
由 Tim Neutkens 提交于
-
由 Tobias Koppers 提交于
fixes #23125 fixes https://github.com/tailwindlabs/tailwindcss-jit/issues/54 ## Bug - [ ] Related issues linked using `fixes #number` - [ ] Integration tests added ## 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. ## Documentation / Examples - [ ] Make sure the linting passes
-
由 Julien Karst 提交于
This pull request add typescript to the current redux-toolkit example on next.js. @markerikson suggested this nice idea to add a ts example: https://twitter.com/acemarke/status/1370877104527712259?s=20 This example is with the previous redux-toolkit example which was more complex. An example with the current example is available here: https://github.com/vercel/next.js/pull/23249 ## Bug - [ ] Related issues linked using `fixes #number` - [ ] Integration tests added ## 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. ## Documentation / Examples - [ ] Make sure the linting passes
-
由 Mito 提交于
Under the Single-Page App (SPA) heading, there is a code snipped which has a missing import: import { useState } from 'react' to import { useState, useEffect } from 'react' Also added apostrophe to description: your old application entry point to your old application's entry point ## Bug - [ ] Related issues linked using `fixes #number` - [ ] Integration tests added ## 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. ## Documentation / Examples - [X] Make sure the linting passes
-
由 Lee Robinson 提交于
-
- 21 3月, 2021 2 次提交
-
-
由 Shu Ding 提交于
Currently Next.js exposes internal code in the error overlay if certain errors were created from the user code. Some examples were attached in #20776. We can clearly see that the path is wrong (`../next-server`), it should be `./node_modules/next/dist/next-server`: ![CleanShot 2021-03-19 at 01 33 04](https://user-images.githubusercontent.com/3676859/111670728-1ae7e400-8853-11eb-9213-3b359798900e.png) The root cause is the `__nextjs_original-stack-frame` middleware resolves the file path with the following code: ```js path.resolve( rootDirectory, getSourcePath(sourcePosition.source) ) ``` where `rootDirectory` is the **app root**, but `sourcePosition.source` comes from the module path, which is relative to the path of the `next` binary, not the app root. That explains why we see `../next-server` from the error above, because it's relative to `./node_modules/next/bin/next`. Because of that, the resolved result will never have `node_modules` in its path and it won't be filtered by the error overlay in the UI. Here's a screenshot of the frame object in the UI: ![CleanShot 2021-03-18 at 23 01 29@2x](https://user-images.githubusercontent.com/3676859/111670062-65b52c00-8852-11eb-9293-3a6e5b7c4b9b.png) And the filter we use to determine if a frame is expanded or not only depends on `body.originalStackFrame`: ```js expanded: !Boolean( body.originalStackFrame?.file?.includes('node_modules') ?? true ) ``` So this PR also adds `source.file` check to ensure they will be ignored (not necessary because we fixed the path resolving). Fixes #20776.
-
由 Tobias Koppers 提交于
## Bug - [x] Related issues linked using `fixes #number` - [ ] Integration tests added ## 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. ## Documentation / Examples - [ ] Make sure the linting passes Fixes #23240
-
- 20 3月, 2021 5 次提交
-
-
由 Nikita 提交于
-
由 Ciprian Caba 提交于
VERCEL_GIT_COMMIT_SHA is now available by default across all integrations
-
由 Shu Ding 提交于
This PR attempts to provide an option to allow importing TS/TSX from outside of the current Next.js project root directory. Although this goes against the design decision that no source code should be imported from outside of root and [might bring tons of issues](https://github.com/vercel/next.js/issues/19928#issuecomment-741596557), it will still be helpful in some monorepo use cases. This PR assumes that the external files are following the same language syntax rules and under the same tooling versions as the source code inside your project root. And it's also not allowed to enable the `baseUrl` feature in the external directory (as the project should only have 1 import base URL). X-ref: #9474, #15569, #19928, #20374.
-
由 JJ Kasper 提交于
-
由 Tim 提交于
Following commit https://github.com/vercel/next.js/commit/1f5c2c851333b5601cc1e9463253fdad0f0d8883 Adding documentation links to example. ## 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. ## Documentation / Examples - [x ] Make sure the linting passes
-
- 19 3月, 2021 5 次提交
-
-
由 Tim Neutkens 提交于
-
由 Tim Neutkens 提交于
-
由 Sam Ko 提交于
-
由 Tim Neutkens 提交于
-
由 JJ Kasper 提交于
This ensures we exit the build process after the build completes even if timers/connections are left open since this can cause the process to hang indefinitely. This was the previous behavior although got changed un-intentionally in https://github.com/vercel/next.js/commit/e27b7e996d6e7e6772272f3d189ce93dac25fc3d This updates our production test with an open timer to ensure it doesn't block the process from completing.
-