1. 02 Jul, 2022 1 commit
  2. 01 Jul, 2022 2 commits
    • Jiachi Liu's avatar
      Alias react and react-dom by default (#38245) · bfaffbdd
      Jiachi Liu authored
      Previously we use custom webpack alias for specific react versions for non server side node runtime aliases. This PR alias the entire folders of `react/` and `react-dom/` so that no more alias in next.config is required but only the nodejs require hook.
      
      * Alias `react` and `react-dom` by default
      * Use `react@experimental` to run server components integration test
      * Drop with-react-17 test util, add `__NEXT_REACT_CHANNEL` as an env var for testing and development to specify the react channel is 17 or new experimental version
      bfaffbdd
    • JJ Kasper's avatar
      Ensure page.server.js matches correctly (#38236) · a1504f4c
      JJ Kasper authored
      * Ensure app/page.server.js matches correctly
      
      * update check
      a1504f4c
  3. 30 Jun, 2022 11 commits
  4. 29 Jun, 2022 23 commits
  5. 28 Jun, 2022 3 commits
    • OJ Kwon's avatar
      feat(next/swc): setup native next-swc crash reporter (#38076) · 42e33655
      OJ Kwon authored
      
      
      This PR attempts to setup native crash reporter for `next-swc`. Currently, it uses sentry internally, but it is subject to change depending on the usecase & needs. In any case it won't be breaking changes since this is not transparent to the end users.
      
      PR sets up basic, minimal setup to collect crash reports only at the moment. We may want to expand & collect more data in native next-swc, but it is not clear what we need to collect / and I believe most cases next.js's js context can collect those data via existing telemetry. Crash report is an exception native handler can perform much better by having it in native context directly. While this is sent to different endpoint than telemetry, it is considered as same opt-in configuration. If telemetry is disabled, crash reporter won't collect as well. 
      
      The information collected by the reporter is minimally configured by sentry's sdk. These are the informations collected for example: 
      
      - device arch / family / model
      - os kernel version / name / version
      - runtime (rust) version / channel
      - sentry sdk
      - panic backtrace
      - next.js release version
      - device host name
      
      There's no per-system uuid configurations yet.
      
      It may need some audit if we need to omit some data included in above, while most of them seems ok to me.
      
      ## Bug
      
      - [ ] Related issues linked using `fixes #number`
      - [ ] Integration tests added
      - [ ] Errors have helpful link attached, see `contributing.md`
      
      ## Feature
      
      - [x] 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 `pnpm lint`
      - [ ] The examples guidelines are followed from [our contributing doc](https://github.com/vercel/next.js/blob/canary/contributing.md#adding-examples)
      42e33655
    • OJ Kwon's avatar
      fix(next/config): update default config for the experimental (#38123) · a3ffd1ce
      OJ Kwon authored
      
      
      Minor fix to recent experimental configs. While the latest next.js includes support for those experimental features, currently it emits warnings like
      
      ```
      You have defined experimental feature (swcPlugins) in next.config.js that does not exist in this version of Next.js
      ```
      
      As validation checks the existence of default values even though config itself allows them to be optional. PR does not attempt to change validation logics, only amends it by having empty default values.
      
      ## 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 `pnpm lint`
      - [ ] The examples guidelines are followed from [our contributing doc](https://github.com/vercel/next.js/blob/canary/contributing.md#adding-examples)
      a3ffd1ce
    • JJ Kasper's avatar
      cb2ba0c7