1. 28 Apr, 2021 5 commits
    • JJ Kasper's avatar
      v10.2.0 · 6b97bcea
      JJ Kasper authored
      6b97bcea
    • JJ Kasper's avatar
      v10.1.4-canary.18 · 0abbb75b
      JJ Kasper authored
      0abbb75b
    • Tim Neutkens's avatar
      Upgrade postcss (#24546) · b26077bd
      Tim Neutkens authored
      Fixes #24421
      
      
      
      ## Bug
      
      - [x] Related issues linked using `fixes #number`
      - [ ] Integration tests added
      
      Can't add an integration test currently, we'll add Node 16 tests later.
      
      ## 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
      b26077bd
    • Tim Neutkens's avatar
      Test fixes for Babel mode (#24312) · 53c19ff1
      Tim Neutkens authored
      * Try enabling Babel turbo mode
      
      * Pass config file explicitly to babel turbo loader.
      
      * Update NextBabelLoaderOptions to use `configFile` instead of `babelrc`.
      
      * Re-add support for options passed to next/babel preset with new babel loader.
      
      * Load babel config files depending on their file extension.
      
      * Include `next/babel` if no Babel config is provided.
      
      * Minor cleanup.
      
      * Avoid duplicate `next/babel` entries.
      
      * No need to pass configFile anymore.
      
      * Fix multiple small issues in merging loader opts with cached config.
      
      * Remove redundant logging (that also breaks a test).
      
      * Include file extension CharacteristicsGermaneToCaching.
      
      * bump
      
      * Disable turboMode now that tests pass
      Co-authored-by: 's avatarDale Bustad <dale@divmain.com>
      53c19ff1
    • JJ Kasper's avatar
      Remove experimental note for has routes (#24529) · f3d51838
      JJ Kasper authored
      This removes the warnings/notes for the `has` custom-routes feature being experimental
      
      ## Documentation / Examples
      
      - [x] Make sure the linting passes
      f3d51838
  2. 27 Apr, 2021 3 commits
    • Mario Souto's avatar
      feat: bump styled-components lib version examples (#24482) · 5de5e49b
      Mario Souto authored
      
      Hi folks I know many people that use that example and it could be using the new version of React to be according with the NextJS v11 
      
      ## Documentation / Examples
      
      - [ ] Make sure the linting passes
      - [ ] Make sure that the bumped up versions are okay
      5de5e49b
    • JJ Kasper's avatar
      v10.1.4-canary.17 · 0f2bd4f2
      JJ Kasper authored
      0f2bd4f2
    • JJ Kasper's avatar
      Ensure stalled CSS triggers fallback navigation (#24488) · efa58efd
      JJ Kasper authored
      This ensures when CSS requests stall that they are included in the route load timeout so that stalled CSS requests don't block us from falling back to a hard navigation. This handles a rare case noticed by @pacocoursey where a transition did not complete while attempting to load CSS assets. 
      
      ## Bug
      
      - [ ] Related issues linked using `fixes #number`
      - [x] Integration tests added
      efa58efd
  3. 26 Apr, 2021 3 commits
    • Janicklas Ralph's avatar
      Font optimization bug fix (#24162) · fff183c4
      Janicklas Ralph authored
      
      
      ## Bug
      
      - [x] Related issues linked using `fixes #23896`
      - [x] Integration tests added
      
      Fixes #23896
      fff183c4
    • Jerry K Jia's avatar
      Fix: Object Destructuring Error (#24397) · fc538790
      Jerry K Jia authored
      According to the official Next.js documentation on [Environmental Variables](https://nextjs.org/docs/basic-features/environment-variables): 
      > `process.env` is not a standard JavaScript object, so you’re not able to use object destructuring. Environment variables must be referenced as e.g. `process.env.NEXT_PUBLIC_PUBLISHABLE_KEY`, not `const { NEXT_PUBLIC_PUBLISHABLE_KEY } = process.env`.
      
      <!--
      Thanks for opening a PR! Your contribution is much appreciated.
      In order to make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below.
      Choose the right checklist for the change that you're making:
      -->
      
      ## 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
      fc538790
    • JJ Kasper's avatar
      Ensure proxy rewrite does not hang on error (#24394) · cac9ccf9
      JJ Kasper authored
      * Ensure proxy rewrite does not hang on error
      
      * remove logs
      
      * Listen to req close
      cac9ccf9
  4. 25 Apr, 2021 3 commits
  5. 24 Apr, 2021 1 commit
  6. 23 Apr, 2021 5 commits
  7. 22 Apr, 2021 9 commits
    • Joe Haddad's avatar
      experimental: remove legacy plugin system (#20759) · 079c6291
      Joe Haddad authored
      * chore: remove old plugins implementation
      
      * chore: remove `onErrorMiddleware`
      
      * Reduce allowed middleware
      
      * remove collect plugins file
      
      * remove old tests
      
      * remove old demo packages
      079c6291
    • Gerald Monaco's avatar
    • JJ Kasper's avatar
      v10.1.4-canary.15 · 1e9f4593
      JJ Kasper authored
      1e9f4593
    • Shu Ding's avatar
      Fix not exposing server errors in hot reloader (#24331) · 6cd1c874
      Shu Ding authored
      Fixes #24056.
      
      ## 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
      6cd1c874
    • JJ Kasper's avatar
      Ensure dev overlay is triggered for more _app/_document errors (#24328) · 85d87a37
      JJ Kasper authored
      This expands on https://github.com/vercel/next.js/issues/24070 and ensures we show the dev overlay for additional cases like where `_app` or `_document` have syntax errors causing compilation to not be able to complete. This achieves showing the dev overlay even when compilation fails from a syntax error by doing a third minimal compilation in development with the needed client-side assets to render the dev overlay. 
      
      ## Bug
      
      - [x] Related issues linked using `fixes #number`
      - [x] Integration tests added
      
      x-ref: https://github.com/vercel/next.js/issues/24070
      85d87a37
    • Jarrod Watts's avatar
      Update with-aws-amplify-typescript example (#24292) · c481147b
      Jarrod Watts authored
      - Update the Readme to use the latest Amplify CLI versions' prompts
      - Update the example to use the [SSR features of AWS Amplify ](https://aws.amazon.com/blogs/mobile/ssr-support-for-aws-amplify-javascript-libraries/)
      - Update to use Next version `10` instead of `9`
      - Correctly use the types produced by the Amplify CLI in `API.ts`
      - Add `amplify auth`  and auth rules to the GraphQL model as suggested by the Amplify CLI.
      c481147b
    • JJ Kasper's avatar
      Bump next-babel-loader cache key (#24335) · 1caa7f49
      JJ Kasper authored
      This bumps the babel cache key since we modified the `react-loadable` babel plugin and we don't want any cached versions used since the module names generated in previous cached version won't match the newly expected values. 
      
      x-ref: https://github.com/vercel/next.js/pull/24281 
      
      ## 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
      1caa7f49
    • Janicklas Ralph's avatar
      Adding script loader files to package.json (#24326) · 9edb1ef1
      Janicklas Ralph authored
      Adding script loader files to package.json
      9edb1ef1
    • Kyle Marshall's avatar
      Ensure locale key not duplicated when navigating back to root path with a query… · a29d8c9e
      Kyle Marshall authored
      Ensure locale key not duplicated when navigating back to root path with a query or hash value (#24323)
      
      This ensures that a duplicate locale key is not prepended to the path when navigating back (using browsers back button) to the root path containing query parameters or a hash value.
      
      Current behaviour:
      * `/fr?value=1` -> `/fr/another` -> click browser back button -> `/fr/fr?value=1`
      * `/fr?value=1` -> `/fr?value=2` -> click browser back button -> `/fr/fr?value=1`
      * `/fr#section` -> `/fr/another` -> click browser back button -> `/fr/fr#section`
      * `/fr#section` -> `/fr#another` -> click browser back button -> `/fr/fr#section`
      
      Fix:
      Remove query string or hash value from path before determining whether to add the locale to the path in `addLocale` function.
      
      ## Bug
      
      - [x] Related issues linked using `fixes #number`
      - [x] Integration tests added
      
      Fixes: #24287 
      a29d8c9e
  8. 21 Apr, 2021 8 commits
  9. 20 Apr, 2021 3 commits