- 11 12月, 2020 2 次提交
-
-
由 Joe Haddad 提交于
-
由 Joe Haddad 提交于
Fixes #18056
-
- 09 12月, 2020 1 次提交
-
-
由 Joe Haddad 提交于
-
- 04 12月, 2020 1 次提交
-
-
由 JJ Kasper 提交于
-
- 02 12月, 2020 3 次提交
-
-
由 JJ Kasper 提交于
This updates to the latest version of the `@ampproject/toolbox-optimizer` which contains updates for dependencies to remove the warnings on install from `npm` x-ref: https://github.com/vercel/next.js/pull/18994 Closes: https://github.com/vercel/next.js/issues/17416
-
由 JJ Kasper 提交于
-
由 JJ Kasper 提交于
-
- 24 11月, 2020 3 次提交
-
-
由 Joe Haddad 提交于
-
由 Joe Haddad 提交于
-
由 Joe Haddad 提交于
-
- 23 11月, 2020 1 次提交
-
-
由 Joe Haddad 提交于
-
- 21 11月, 2020 1 次提交
-
-
由 JJ Kasper 提交于
-
- 18 11月, 2020 4 次提交
-
-
由 Joe Haddad 提交于
-
由 Joe Haddad 提交于
-
由 JJ Kasper 提交于
-
由 Joe Haddad 提交于
This fixes compatibility with React 17 and `styled-jsx`. Fixes #19242
-
- 16 11月, 2020 1 次提交
-
-
由 Joe Haddad 提交于
-
- 14 11月, 2020 4 次提交
-
-
由 JJ Kasper 提交于
-
由 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
-
由 Joe Haddad 提交于
-
由 Joe Haddad 提交于
-
- 13 11月, 2020 2 次提交
-
-
由 Joe Haddad 提交于
-
由 Joe Haddad 提交于
-
- 12 11月, 2020 6 次提交
-
-
由 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.
-
由 Joe Haddad 提交于
-
由 Joe Haddad 提交于
-
由 Joe Haddad 提交于
Fixes #18518
-
由 Joe Haddad 提交于
-
由 JJ Kasper 提交于
-
- 11 11月, 2020 2 次提交
-
-
由 JJ Kasper 提交于
Updates to the latest version of `chokidar` x-ref: https://github.com/vercel/next.js/issues/17416
-
由 Joe Haddad 提交于
-
- 10 11月, 2020 2 次提交
-
-
由 Joe Haddad 提交于
-
由 Joe Haddad 提交于
-
- 09 11月, 2020 2 次提交
-
-
由 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>).
-
由 JJ Kasper 提交于
-
- 08 11月, 2020 1 次提交
-
-
由 Joe Haddad 提交于
-
- 07 11月, 2020 2 次提交
-
-
由 JJ Kasper 提交于
-
由 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 2 次提交
-
-
由 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.
-