- 04 8月, 2020 8 次提交
-
-
由 Jonathan G 提交于
Co-authored-by: NTim Neutkens <timneutkens@me.com> Co-authored-by: NJJ Kasper <jj@jjsweb.site>
-
由 Prateek Bhatnagar 提交于
- Fixes the serverless build for font optimizations
-
由 Kristóf Poduszló 提交于
Add missing nomodule polyfills and suggest using features only up to ES2019 for browser compatibility (#15772) These changes aim to resolve most of the concerns raised in #15756. It adds missing polyfills for legacy browsers up until ES2019: - Number.{parseFloat,parseInt} - ~Math.{acosh,asinh,atanh,cbrt,clz32,cosh,expm1,fround,hypot,imul,log10p,log1p,log2,sign,sinh,tanh,trunc}~ _[Removed as these are [not widely used](https://github.com/vercel/next.js/pull/15772#discussion_r463957931)]_ - While these may seem to weigh a lot, they barely add 1 kB to the resulting bundle: <img width="492" alt="gzip: 32 kB vs. 30.9 kB, Brotli: 28.8 kB vs. 27.8 kB" src="https://user-images.githubusercontent.com/14854048/89100961-1376e600-d3fc-11ea-90fd-3e6632b70220.png"> - ~Object.fromEntries~ _[Removed as [it's rarely used in user code](https://github.com/vercel/next.js/pull/15772#discussion_r463984612)]_ Also, the following features are now supported with build-time transforms: - ~`globalThis` (gets transformed into `window` in browser environments)~ _[Removed as it [could break existing applications](https://github.com/vercel/next.js/pull/15772#discussion_r463956269)]_ - `export * as ns from 'module'` The suggested TypeScript library version has been set to ES2018, so the features below become unavailable in type-checked files (they're not evenly supported by module-compatible browsers, either): - Object.fromEntries - String.prototype.matchAll - String.prototype.replaceAll - Promise.any + AggregateError - WeakRef As for the `import.meta` support, [webpack v5 seems to fix that](https://github.com/webpack/webpack/pull/11075), so it should eventually become an issue of the past. --- Fixes #15756
-
由 Joe Haddad 提交于
-
由 Joe Haddad 提交于
-
由 Joe Haddad 提交于
-
由 Joe Haddad 提交于
Fixes #15737
-
由 Marc 提交于
I was referencing the with-passport example and found a minor syntax error:\ The login and signup page both used `event.preventDefault()` on the submit handlers, whereby the correct reference to the event is `e` as defined within the `handleSubmit` functions. Additionally used the chance to bump npm packages, the largest bump being swr to the latest version: 0.3.0 ### Summary of all Changes made: * Fixed syntax error on login page * Fixed syntax error on signup page * Bumped cookie to 0.4.1 * Bumped next-connect to 0.8.1 * Bumped swr to 0.3.0
-
- 03 8月, 2020 9 次提交
-
-
由 Tim Neutkens 提交于
Same as #15483 but couldn't push to it --- Closes #15483 Fixes #15828
-
由 Jan Potoms 提交于
In terms of url rewriting, `trailingSlash` supports everything `exportTrailingSlash` does. We can just share all other code paths and deprecate `exportTrailingSlash`. This PR shows a deprecation warning when `exportTrailingSlash` is used. Also fixes https://github.com/vercel/next.js/issues/15774 We can update the tests now or later. (I kept them the same to prove it's non-breaking) To do: - [x] Do we want to keep this? => nope https://github.com/vercel/next.js/blob/841d4efc517a379d8947f491e3c6a1c4784bbccf/packages/next/next-server/lib/router/router.ts#L329 - [x] I kept `exportTrailingSlash` here. Do we want to rename that as well? => nope https://github.com/vercel/next.js/blob/2d9d649d492b77adeddea0242ab6b7fe73d18079/packages/next/build/index.ts#L959
-
由 Mehedi Hassan 提交于
Following up from #14830, this PR adds a new page to the docs for Create Next App. The content is identical to the README created as part of #14830. Also added a link on the main `getting-started` page to the new docs for Create Next App to help users find more info on Create Next App if needed. I'm unsure as to whether the content for the documentation needs to be different from the one I wrote for the README. Please let me know if that's the case, and I will be happy to tweak the structure.
-
由 Kim T 提交于
Fixes #15802 Added Params type to prevent typescript error during build step
-
由 Tim Neutkens 提交于
- Use latest terser version (still 1 warning in the stable version which is an open PR) - Add emitOnErrors instead of noEmitOnErrors - Added trace-deprecations for Next.js core development
-
由 Tim Neutkens 提交于
- Using `namedChunks` where possible, this will also allow for faster access to the chunks as we no longer have to look them up like we did before using `find` - Using the new asset hooks introduced in the latest webpack beta - Using the new externals function signature
-
由 Joe Haddad 提交于
-
由 JJ Kasper 提交于
Adds additional test cases for cascading env values and corrects behavior Fixes: https://github.com/vercel/next.js/issues/15744
-
由 sreekumar menon 提交于
We should remove the dotenv dependency from all Next.js examples (in favor of Next.js environment support): https://github.com/vercel/next.js/issues/15225
-
- 02 8月, 2020 2 次提交
-
-
由 David Lemayian 提交于
Thank you for the excellent examples. This PR updates the `.gitignore` for [with-electron](https://github.com/vercel/next.js/tree/canary/examples/with-electron) example to ignore the output folders.
-
由 Jan Potoms 提交于
-
- 01 8月, 2020 5 次提交
-
-
由 Sam Robbins 提交于
While it is mentioned in the [link documentation](https://nextjs.org/docs/api-reference/next/link), I think it is useful to also explain in the dynamic route documentation that you need to include the as parameter when routing to a dynamic route/
-
-
由 Joe Haddad 提交于
-
由 Jan Potoms 提交于
Irrelevant since https://github.com/vercel/next.js/pull/15379
-
由 Ronald Stevanus 提交于
## What The current `gh-pages` example has issue when deploying. This is how the error looks like: ![image](https://user-images.githubusercontent.com/1008093/88996697-827f0c80-d320-11ea-93bd-48141c321a65.png) ``` ... Export successful The following paths are ignored by one of your .gitignore files: out hint: Use -f if you really want to add them. hint: Turn this message off by running hint: "git config advice.addIgnoredFile false" npm ERR! code ELIFECYCLE npm ERR! errno 1 npm ERR! next@1.0.0 deploy: `rm -rf node_modules/.cache && next build && next export && touch out/.nojekyll && git add out/` npm ERR! Exit status 1 npm ERR! npm ERR! Failed at the next@1.0.0 deploy script. npm ERR! This is probably not a problem with npm. There is likely additional logging output above. npm ERR! A complete log of this run can be found in: ... ``` It's because `out` folder is added on `.gitignore` and the deploy script runs `git add out/`. The fix is to remove `out` folder from `.gitignore`. ## How was it tested run `npm run deploy`, it should be completed successfully.
-
- 31 7月, 2020 9 次提交
-
-
由 Pierre de la Martinière 提交于
Should prevent some tears when people tries to replicate some example with Next.js 9.5.0 ;) cheers!
-
由 Rafau 提交于
I think this is necessary for IE11. via [Webpack docs](https://webpack.js.org/migrate/5/#turn-off-es2015-syntax-in-runtime-code-if-necessary) > By default, webpack's runtime code uses ES2015 syntax to build smaller bundles. If your build targets environments that don't support this syntax (like IE11), you'll need to set output.ecmaVersion: 5 to revert to ES5 syntax. Thank you
-
由 Jon Espen Kvisler 提交于
next-transpile-modules needs to be updated to support Next.js 9.5 Closes #15725
-
由 Jan Potoms 提交于
Caught this while reviewing router code for https://github.com/vercel/next.js/pull/15710
-
-
由 Jan Potoms 提交于
Saw this one fail on azure
-
由 JJ Kasper 提交于
This adds an example of using regex matching for custom routes Fixes https://github.com/vercel/next.js/issues/15712
-
由 matamatanot 提交于
You have been redirected to the`/home` page. I'm not sure if that's correct, but it's been fixed to move the link to the document. https://vercel.com/smart-cdn https://vercel.com/docs/v2/edge-network/overview
-
由 Luis Alvarez D 提交于
-
- 30 7月, 2020 7 次提交
-
-
由 Luis Alvarez D 提交于
-
由 Joe Haddad 提交于
Fixes #15668
-
由 Arsalan Khattak 提交于
-
由 JJ Kasper 提交于
`pageProps` should always be defined to ensure everything is working as expected although to prevent a breaking change this adds an additional check before attempting to access `pageProps` before hydration. It also adds tests to prevent regressing on this Closes: https://github.com/vercel/next.js/issues/15647
-
由 Joe Haddad 提交于
-
由 Joe Haddad 提交于
-
由 Joe Haddad 提交于
-