- 14 11月, 2020 1 次提交
-
-
由 Joe Haddad 提交于
We accidentally regressed back in 9.5 and dropped support for inline CSS comments. PostCSS always parses these as pass-through (and not a syntax error), which can cause problems when minifying. Browsers do a similar thing and ignore the comments. To ensure we generate valid CSS, this adds support for stripping the CSS comments from the build. --- Fixes #15589 Closes #17130
-
- 12 11月, 2020 3 次提交
-
-
由 Josh Flayhart 提交于
In working with @devknoll on https://github.com/vercel/next.js/pull/17770 we thought it would be a good idea to update to the latest minor version from 1.2.20 -> 1.4.9 based on some bug fixes in these minor releases. I would like to separate this out to simplify the growing changeset in https://github.com/vercel/next.js/pull/17770, where we need to use `node-html-parser` to parse HTML for custom react components. The linked changeset above will take some time and there are some [useful bug fixes](https://github.com/taoqf/node-html-parser/commits/master) and features in this minor release we could benefit from anyway. Namely: - add nextSibling, nextElementSibling - missing node tag - `<style>` tag is not parsed correctly Also I think it's a good idea to separate this out for testing.
-
由 Ludovico Fischer 提交于
-
由 Joe Haddad 提交于
Fixes #18518
-
- 11 11月, 2020 1 次提交
-
-
由 JJ Kasper 提交于
Updates to the latest version of `chokidar` x-ref: https://github.com/vercel/next.js/issues/17416
-
- 09 11月, 2020 1 次提交
-
-
由 iczero 提交于
`node-sass` v5 introduced support for Node.js v15, which is not supported by v4. However, Next.js currently errors with ``` Error: Node Sass version 5.0.0 is incompatible with ^4.0.0. ``` when attempting to build with `node-sass` 5.0.0. This error comes from `sass-loader`. They have recently released version 10.0.5 which supports `node-sass` 5.0.0 (PR <https://github.com/webpack-contrib/sass-loader/pull/899>, release <https://github.com/webpack-contrib/sass-loader/releases/tag/v10.0.5>).
-
- 07 11月, 2020 1 次提交
-
-
由 JJ Kasper 提交于
This makes sure we don't use es6 syntax when compiling the `web-vitals` package with `ncc` since that breaks IE11 compatibility x-ref: https://github.com/vercel/ncc/pull/614
-
- 06 11月, 2020 4 次提交
-
-
由 Joe Haddad 提交于
Fixes #17066
-
由 Guy Bedford 提交于
This upgrades to ncc@0.25.0 and fixes the previous bugs including: * ncc not referenced correctly in build * Babel type errors * node-fetch, etag, chalk and raw-body dependencies not building with ncc - these have been "un-ncc'd" for now. As they are relatively small dependencies, this doesn't seem too much of an issue and we can follow up in the tracking ncc issue at https://github.com/vercel/ncc/issues/612. * `yarn dev` issues Took a lot of bisecting, but the overall diff isn't too bad here in the end.
-
由 Guy Bedford 提交于
This fixes the current regression with an ncc revert for now. I will continue to follow up with the ncc upgrade in https://github.com/vercel/next.js/pull/18860.
-
由 JJ Kasper 提交于
* Fix chromedriver set-up to test electron separately * Update workflow * Update compiled
-
- 05 11月, 2020 3 次提交
-
-
由 Guy Bedford 提交于
This adds inlining for Babel and the Babel plugins used in next. This is based to the PR at https://github.com/vercel/next.js/pull/18823. The approach is to make one large bundle and then separate out the individual packages from that in order to avoid duplications. In the first attempt the Babel bundle size was 10MB... using "resolutions" in the Yarn workspace to reduce the duplicated packages this was brought down to a 2.8MB bundle for Babel and all the used plugins which is exactly the expected file size here. This will thus add a 2.8MB download size to the next package, but save downloading any babel dependencies separately, removing a large number of package dependencies from the overall install.
-
由 Guy Bedford 提交于
This updates to the latest ncc@0.24.1 release. Initially I thought chalk needed to be removed to make this work, but it turns out it was a caching issue. I've also added a cache clear to the rebuild command to avoid these issues hopefully in future.
-
- 04 11月, 2020 2 次提交
-
-
由 Guy Bedford 提交于
This is a prerequisite to being able to ncc inline the Babel dependencies in next.js. The removal of preset-modules is based on replacing it with preset-env under `targets: { esmodules: true }`, as per the guidance from the package (https://www.npmjs.com/package/@babel/preset-modules): > Starting from @babel/preset-env 7.9.0, you can enable the bugfixes: true option to get the same behavior as using @babel/preset-modules, but with support for custom targets. If you need to target browsers with native modules support (like this preset does), you can use targets: { esmodules: true }. From the above, I'm pretty sure this is entirely a backwards compatible change, apart from the change to the runtime plugin list being visible. Perhaps @developit can confirm this as well.
-
由 Cowboy Ho 提交于
Co-authored-by: NTim Neutkens <timneutkens@me.com> Co-authored-by: NJoe Haddad <joe.haddad@zeit.co> Co-authored-by: NJJ Kasper <jj@jjsweb.site>
-
- 25 10月, 2020 2 次提交
-
-
由 Tim Neutkens 提交于
-
由 JJ Kasper 提交于
This ensures a custom `/404` page with `getStaticProps` works correctly when leveraging the new `unstable_notFound` support in `getStaticProps` Closes: https://github.com/vercel/next.js/issues/18196 x-ref: https://github.com/vercel/next.js/pull/17755
-
- 23 10月, 2020 2 次提交
-
-
由 dependabot[bot] 提交于
Bumps [node-sass](https://github.com/sass/node-sass) from 4.12.0 to 4.13.1. - [Release notes](https://github.com/sass/node-sass/releases) - [Changelog](https://github.com/sass/node-sass/blob/master/CHANGELOG.md) - [Commits](https://github.com/sass/node-sass/compare/v4.12.0...v4.13.1) Signed-off-by: Ndependabot[bot] <support@github.com> Co-authored-by: Ndependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
-
由 dependabot[bot] 提交于
Bumps [tree-kill](https://github.com/pkrumins/node-tree-kill) from 1.2.1 to 1.2.2. - [Release notes](https://github.com/pkrumins/node-tree-kill/releases) - [Commits](https://github.com/pkrumins/node-tree-kill/compare/v1.2.1...v1.2.2) Signed-off-by: Ndependabot[bot] <support@github.com> Co-authored-by: Ndependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: Nkodiakhq[bot] <49736102+kodiakhq[bot]@users.noreply.github.com>
-
- 22 10月, 2020 2 次提交
-
-
由 Tim Neutkens 提交于
Solves the build failure we're seeing on PRs
-
由 Tim Neutkens 提交于
Fixes #18044 Related to #17416
-
- 21 10月, 2020 3 次提交
-
-
由 Ludovico Fischer 提交于
Co-authored-by: NTim Neutkens <tim@timneutkens.nl>
-
由 Ludovico Fischer 提交于
Co-authored-by: NTim Neutkens <timneutkens@me.com> Co-authored-by: Nkodiakhq[bot] <49736102+kodiakhq[bot]@users.noreply.github.com>
-
由 Felipe Flores 提交于
Bump resolve-url-loader version to fix vulnerability. Fixes #18048 Related #18044
-
- 19 10月, 2020 1 次提交
-
-
由 Ludovico Fischer 提交于
Co-authored-by: NTim Neutkens <timneutkens@me.com> Co-authored-by: Nkodiakhq[bot] <49736102+kodiakhq[bot]@users.noreply.github.com>
-
- 18 10月, 2020 1 次提交
-
-
由 JJ Kasper 提交于
This makes sure the image optimizer doesn't de-animate images by transforming them with sharp since sharp doesn't currently handle outputting animated images x-ref: https://github.com/vercel/next.js/pull/17749
-
- 16 10月, 2020 1 次提交
-
-
由 Steven 提交于
Co-authored-by: NJJ Kasper <jj@jjsweb.site>
-
- 14 10月, 2020 1 次提交
-
-
由 Tommaso De Rossi 提交于
Co-authored-by: NLuis Alvarez D <luis@vercel.com> Co-authored-by: NTim Neutkens <tim@timneutkens.nl>
-
- 08 10月, 2020 1 次提交
-
-
由 JJ Kasper 提交于
This adds the initial changes outlined in the [i18n routing RFC](https://github.com/vercel/next.js/discussions/17078). This currently treats the locale prefix on routes similar to how the basePath is treated in that the config doesn't require any changes to your pages directory and is automatically stripped/added based on the detected locale that should be used. Currently redirecting occurs on the `/` route if a locale is detected regardless of if an optional catch-all route would match the `/` route or not we may want to investigate whether we want to disable this redirection automatically if an `/index.js` file isn't present at root of the pages directory. TODO: - [x] ensure locale detection/populating works in serverless mode correctly - [x] add tests for locale handling in different modes, fallback/getStaticProps/getServerSideProps To be continued in fall-up PRs - [ ] add tests for revalidate, auto-export, basePath + i18n - [ ] add mapping of domains with locales - [ ] investigate detecting locale against non-index routes and populating the locale in a cookie x-ref: https://github.com/vercel/next.js/issues/17110
-
- 15 9月, 2020 1 次提交
-
-
由 Joe Haddad 提交于
-
- 13 9月, 2020 1 次提交
-
-
由 Bogdan Chadkin 提交于
For some reason babel-plugin-syntax-jsx of babel 6 was used instead of babel 7 version.
-
- 12 9月, 2020 2 次提交
-
-
由 Ole-Martin Bratteng 提交于
ref https://github.com/GoogleChrome/web-vitals/pull/68 won't fail the new [`no-unload-listeners`](https://github.com/GoogleChrome/lighthouse/pull/11085) Lighthouse audit.
-
由 Bogdan Chadkin 提交于
Ref https://github.com/webpack-contrib/terser-webpack-plugin/blob/v4.1.0/package.json#L44 cacache is a dependency of terser-webpack-plugin. The latest version depends on cacache 15 while next adds cacache 13. This may give unexpected results. Better keep it in sync with terser plugin.
-
- 11 9月, 2020 3 次提交
-
-
由 Bogdan Chadkin 提交于
Babel-preset-env includes includes optional chaining and nullish-coalescing since [7.8.0](https://github.com/babel/babel/releases/tag/v7.8.0). In this diff I removed these plugins from next preset to prevent dependency duplication when their newer versions are out.
-
由 Bogdan Chadkin 提交于
The new version replaced big clone-deep package with dependency-free klona - https://github.com/webpack-contrib/sass-loader/releases/tag/v10.0.0 - https://github.com/webpack-contrib/sass-loader/releases/tag/v9.0.0 Also deduped some related transitives.
-
由 Sakito Mukai 提交于
There was a security update for node-fetch. > This is an important security release. It is strongly recommended to update as soon as possible. https://github.com/node-fetch/node-fetch/blob/master/docs/CHANGELOG.md#v261
-
- 10 9月, 2020 1 次提交
-
-
由 Joe Haddad 提交于
Fixes #10142 Fixes #11629
-
- 02 9月, 2020 1 次提交
-
-
由 JJ Kasper 提交于
Since the error overlay could be dismissed before this is resolved we need to make sure the component is still mounted before updating the state.
-
- 01 9月, 2020 1 次提交
-
-
由 Joe Haddad 提交于
-