1. 31 Mar, 2022 4 commits
  2. 30 Mar, 2022 19 commits
  3. 29 Mar, 2022 1 commit
    • hiro's avatar
      Fix typos (#35683) · a00268e7
      hiro authored
      * fix(typo): wolrd -> world
      
      * fix(typo): _lineNumer -> _lineNumber
      
      * fix(typo): Dyanmic -> Dynamic
      
      * fix(typo): mutliple -> multiple
      
      * fix(typo): dyanmic -> dynamic
      
      * fix(typo): speical -> special
      
      * fix(typo): acceptible -> acceptable
      
      * fix(typo): dyanmic -> dynamic
      
      * fix(typo): nonexistant -> nonexistent
      
      * fix(typo): nonexistant -> nonexistent
      
      * fix(typo): nonexistant -> nonexistent
      
      * fix(typo): nonexistant -> nonexistent
      
      * fix(typo): nonexistant -> nonexistent
      
      * fix(typo): nonexistant -> nonexistent
      
      * fix(typo): accesible -> accessible
      
      * fix(typo): explicitely -> explicitly
      a00268e7
  4. 28 Mar, 2022 15 commits
    • JJ Kasper's avatar
      v12.1.3-canary.0 · 88a7e584
      JJ Kasper authored
      88a7e584
    • Seth Falco's avatar
      fix: don't override user-agent in fetch if specified (#35547) · ad7cb3b2
      Seth Falco authored
      * fix: don't override user-agent in fetch if specified
      
      * Add test for fetch user-agent in middleware
      Co-authored-by: 's avatarJJ Kasper <jj@jjsweb.site>
      ad7cb3b2
    • OJ Kwon's avatar
      test(integration): emit console error when test fails (#35507) · abfbf41e
      OJ Kwon authored
      
      
      Minor improvements to the integration test runner to emit process's stdout when its execution failed.
      
      We have `console.log` for the output, but it doesn't emit actually since jest suppresses console output unlesss _assertion_ fails. If we throws in `before*` hook, since there's no actual assertion fails jest won't release captured console logs.
      
      PR adds one straightforward workaround (https://stackoverflow.com/questions/48695717/console-log-statements-output-nothing-at-all-in-jest) to emit if process exits with non-zero errorcode. To avoid any existing behavior, this is not enabled for the cases when process successfully exits.
      
      ## Bug
      
      - [ ] Related issues linked using `fixes #number`
      - [ ] Integration tests added
      - [ ] Errors have helpful link attached, see `contributing.md`
      
      ## 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`
      - [x] Integration tests added
      - [ ] Documentation added
      - [ ] Telemetry added. In case of a feature if it's used or not.
      - [ ] Errors have helpful link attached, see `contributing.md`
      
      ## Documentation / Examples
      
      - [ ] Make sure the linting passes by running `yarn lint`
      abfbf41e
    • Naoyuki Kanezawa's avatar
      fix the dynamic routing of middleware (#32601) · 53d1b00c
      Naoyuki Kanezawa authored
      * fix the dynamic routing of middleware
      
      * add middleware to dynamicRoutes of routes-manifest
      
      * remove unused import
      
      * fix middleware routing with static paths
      
      * update manifest version test
      
      * prevent to match with api route using regex
      
      * use iterator instead of generator
      
      * do not use Iterator
      
      * fix type
      
      * fix type
      
      * remove unused import
      
      * apply the fix for support colons
      Co-authored-by: 's avatarJJ Kasper <jj@jjsweb.site>
      53d1b00c
    • Luis Alvarez D's avatar
      Add deprecated JSDoc comments for the previous middleware signature (#35448) · 5d1f33f5
      Luis Alvarez D authored
      Something I noticed while using Middleware is that the older and no longer working methods are still accessible for the `event` with autocompletion because of their types, and the way of knowing they're deprecated is by running the app and seeing the error message, this should improve that when coding in tools like VS Code.
      
      ## 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.
      - [ ] Errors have helpful link attached, see `contributing.md`
      
      ## Documentation / Examples
      
      - [ ] Make sure the linting passes by running `yarn lint`
      Co-authored-by: 's avatarJJ Kasper <22380829+ijjk@users.noreply.github.com>
      5d1f33f5
    • JJ Kasper's avatar
      Update default test timeouts for yarn install times (#35669) · 6a4c70e0
      JJ Kasper authored
      This updates our default test times as discussed to account for longer `yarn install` times for the isolated tests as GitHub actions network can be slow. 
      
      x-ref: https://github.com/vercel/next.js/pull/35507#issuecomment-1074606737
      x-ref: [slack thread](https://vercel.slack.com/archives/CGU8HUTUH/p1647919982840099)
      6a4c70e0
    • JJ Kasper's avatar
      3d5a9bf5
    • JJ Kasper's avatar
      v12.1.2 · 50be7cc1
      JJ Kasper authored
      50be7cc1
    • JJ Kasper's avatar
      v12.1.2-canary.1 · 82542549
      JJ Kasper authored
      82542549
    • JJ Kasper's avatar
      Ensure eslint plugins dont conflict (#35667) · 12e1bb7d
      JJ Kasper authored
      12e1bb7d
    • Tim Neutkens's avatar
      Rename createRSCHook to createFlightHook (#35665) · 65680ba3
      Tim Neutkens authored
      
      
      Updates the naming of these to be in line with what it does.
      
      ## Bug
      
      - [ ] Related issues linked using `fixes #number`
      - [ ] Integration tests added
      - [ ] Errors have helpful link attached, see `contributing.md`
      
      ## 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.
      - [ ] Errors have helpful link attached, see `contributing.md`
      
      ## Documentation / Examples
      
      - [ ] Make sure the linting passes by running `yarn lint`
      65680ba3
    • Luis Alvarez D's avatar
      Update middleware examples list (#35622) · ab119bcc
      Luis Alvarez D authored
      Logging and analytics are not provided in vercel/examples using middleware.
      
      
      
      ## Bug
      
      - [ ] Related issues linked using `fixes #number`
      - [ ] Integration tests added
      - [ ] Errors have helpful link attached, see `contributing.md`
      
      ## 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.
      - [ ] Errors have helpful link attached, see `contributing.md`
      
      ## Documentation / Examples
      
      - [ ] Make sure the linting passes by running `yarn lint`
      ab119bcc
    • Shu Ding's avatar
      Fix server component render condition (#35663) · f5917ad3
      Shu Ding authored
      We are currently using `!!ComponentMod.__next_rsc__` as the hint for the renderer to tell if the component is a server component, however that export field (`__next_rsc__`) is assigned to client components (`.client.[ext]`) as well. 
      
      This PR adds a new `__next_rsc_server__` field which is only true when the component is a server component so the renderer can handle client components correctly.
      
      ## Bug
      
      - [ ] Related issues linked using `fixes #number`
      - [ ] Integration tests added
      - [ ] Errors have helpful link attached, see `contributing.md`
      
      ## 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.
      - [ ] Errors have helpful link attached, see `contributing.md`
      
      ## Documentation / Examples
      
      - [ ] Make sure the linting passes by running `yarn lint`
      f5917ad3
    • Jiachi Liu's avatar
      Clean up legacy react 18 tests (#35615) · 41a2eb23
      Jiachi Liu authored
      ### source changes
      * Error dynamic suspense option in non concurrent mode, don't check react root anymore since they should be bound
      
      ### tests changes
      
      * Remove duplicated rsc client test
      * Merge type checking cases (`next/dynamic`)
      * Remove blocking rendering tests cases since we should opt-in Fizz rendering when using React.lazy
      * Remove some thrown promises cases, leverage the streaming component we had in RSC test
      41a2eb23
    • Jiachi Liu's avatar
      enhance: detect ESM by ast type (#35627) · 4bfcf834
      Jiachi Liu authored
      Simplify the esmodule detection. If there's any import/exprt usage, it will return `Module` in ast.type otherwise `Script` when `isModule` is set to `"unknown"`
      4bfcf834
  5. 27 Mar, 2022 1 commit
    • TianenPang's avatar
      Fix typo in rewrites docs (#35639) · 0d401ddc
      TianenPang authored
      Correct the type of `trailingSlash` in config example
      
      Modified: `docs/api-reference/next.config.js/rewrites.md`
      
      ```diff
      - trailingSlash: 'true',
      + trailingSlash: true,
      ```
      0d401ddc