Skip to content

React Aliases #57283

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Oct 23, 2023
Merged

React Aliases #57283

merged 2 commits into from
Oct 23, 2023

Conversation

wyattjoh
Copy link
Member

@wyattjoh wyattjoh commented Oct 23, 2023

This adds aliases to the new react packages being used by Next.js.

@wyattjoh
Copy link
Member Author

wyattjoh commented Oct 23, 2023

Current dependencies on/for this PR:

This comment was auto-generated by Graphite.

@wyattjoh wyattjoh changed the title React Bump React Aliases Oct 23, 2023
@ijjk
Copy link
Member

ijjk commented Oct 23, 2023

Tests Passed

@ijjk
Copy link
Member

ijjk commented Oct 23, 2023

Stats from current PR

Default Build (Increase detected ⚠️)
General Overall increase ⚠️
vercel/next.js canary vercel/next.js refactor/react-bump Change
buildDuration 12.8s 13.1s ⚠️ +246ms
buildDurationCached 7.6s 7.8s ⚠️ +155ms
nodeModulesSize 174 MB 178 MB ⚠️ +3.05 MB
nextStartRea..uration (ms) 454ms 457ms N/A
Client Bundles (main, webpack)
vercel/next.js canary vercel/next.js refactor/react-bump Change
199-HASH.js gzip 27.9 kB 27.9 kB N/A
3f784ff6-HASH.js gzip 53.2 kB 53.2 kB N/A
99.HASH.js gzip 182 B 182 B
framework-HASH.js gzip 45.5 kB 45.5 kB
main-app-HASH.js gzip 254 B 252 B N/A
main-HASH.js gzip 33 kB 33 kB N/A
webpack-HASH.js gzip 1.75 kB 1.75 kB N/A
Overall change 45.7 kB 45.7 kB
Legacy Client Bundles (polyfills)
vercel/next.js canary vercel/next.js refactor/react-bump Change
polyfills-HASH.js gzip 31 kB 31 kB
Overall change 31 kB 31 kB
Client Pages
vercel/next.js canary vercel/next.js refactor/react-bump Change
_app-HASH.js gzip 206 B 205 B N/A
_error-HASH.js gzip 182 B 180 B N/A
amp-HASH.js gzip 506 B 505 B N/A
css-HASH.js gzip 322 B 323 B N/A
dynamic-HASH.js gzip 2.59 kB 2.59 kB
edge-ssr-HASH.js gzip 260 B 259 B N/A
head-HASH.js gzip 350 B 350 B
hooks-HASH.js gzip 369 B 369 B
image-HASH.js gzip 4.38 kB 4.38 kB N/A
index-HASH.js gzip 256 B 256 B
link-HASH.js gzip 2.67 kB 2.67 kB N/A
routerDirect..HASH.js gzip 316 B 318 B N/A
script-HASH.js gzip 385 B 384 B N/A
withRouter-HASH.js gzip 319 B 319 B
1afbb74e6ecf..834.css gzip 106 B 106 B
Overall change 3.99 kB 3.99 kB
Client Build Manifests
vercel/next.js canary vercel/next.js refactor/react-bump Change
_buildManifest.js gzip 484 B 482 B N/A
Overall change 0 B 0 B
Rendered Page Sizes
vercel/next.js canary vercel/next.js refactor/react-bump Change
index.html gzip 528 B 529 B N/A
link.html gzip 541 B 541 B
withRouter.html gzip 523 B 522 B N/A
Overall change 541 B 541 B
Edge SSR bundle Size
vercel/next.js canary vercel/next.js refactor/react-bump Change
edge-ssr.js gzip 95.3 kB 95.3 kB N/A
page.js gzip 158 kB 158 kB N/A
Overall change 0 B 0 B
Middleware size
vercel/next.js canary vercel/next.js refactor/react-bump Change
middleware-b..fest.js gzip 624 B 623 B N/A
middleware-r..fest.js gzip 150 B 151 B N/A
middleware.js gzip 22.9 kB 22.9 kB N/A
edge-runtime..pack.js gzip 1.92 kB 1.92 kB
Overall change 1.92 kB 1.92 kB
Commit: f70afd1

@wyattjoh wyattjoh force-pushed the refactor/revalidate branch from 6e909cc to a90d627 Compare October 23, 2023 19:17
Base automatically changed from refactor/revalidate to canary October 23, 2023 19:37
@wyattjoh wyattjoh force-pushed the refactor/react-bump branch from 3d1fe2d to 16ba3dd Compare October 23, 2023 19:45
@wyattjoh wyattjoh marked this pull request as ready for review October 23, 2023 19:46
@wyattjoh wyattjoh force-pushed the refactor/react-bump branch from 16ba3dd to 7468287 Compare October 23, 2023 19:46
@wyattjoh wyattjoh mentioned this pull request Oct 23, 2023
Copy link
Contributor

@gnoff gnoff left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I noticed our swc taskfile is targeting node 16 still. Aren't we bumping minimum node version to 18 with next 14? maybe we should bump this too?

Comment on lines +103 to +111
baseUrl: __dirname,
paths: {
'react-dom/server.edge': [
'./compiled/react-dom-experimental/server.edge',
],
'react-dom/static.edge': [
'./compiled/react-dom-experimental/static.edge',
],
},
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've not seen us do this kind of aliasing for react before. Why is this required for this PR?

@kodiakhq kodiakhq bot merged commit 9f512f1 into canary Oct 23, 2023
@kodiakhq kodiakhq bot deleted the refactor/react-bump branch October 23, 2023 21:04
feedthejim added a commit that referenced this pull request Oct 23, 2023
feedthejim added a commit that referenced this pull request Oct 24, 2023
This reverts commit 9f512f1.

<!-- Thanks for opening a PR! Your contribution is much appreciated.
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(s) that you're making:

## For Contributors

### Improving Documentation

- Run `pnpm prettier-fix` to fix formatting issues before opening the
PR.
- Read the Docs Contribution Guide to ensure your contribution follows
the docs guidelines:
https://nextjs.org/docs/community/contribution-guide

### Adding or Updating Examples

- The "examples guidelines" are followed from our contributing doc
https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md
- Make sure the linting passes by running `pnpm build && pnpm lint`. See
https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md

### Fixing a bug

- Related issues linked using `fixes #number`
- Tests added. See:
https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs
- Errors have a helpful link attached, see
https://github.com/vercel/next.js/blob/canary/contributing.md

### Adding a feature

- Implements an existing feature request or RFC. Make sure the feature
request has been accepted for implementation before opening a PR. (A
discussion must be opened, see
https://github.com/vercel/next.js/discussions/new?category=ideas)
- Related issues/discussions are linked using `fixes #number`
- e2e tests added
(https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs)
- Documentation added
- Telemetry added. In case of a feature if it's used or not.
- Errors have a helpful link attached, see
https://github.com/vercel/next.js/blob/canary/contributing.md


## For Maintainers

- Minimal description (aim for explaining to someone not on the team to
understand the PR)
- When linking to a Slack thread, you might want to share details of the
conclusion
- Link both the Linear (Fixes NEXT-xxx) and the GitHub issues
- Add review comments if necessary to explain to the reviewer the logic
behind a change

### What?

### Why?

### How?

Closes NEXT-
Fixes #

-->

Co-authored-by: kodiakhq[bot] <49736102+kodiakhq[bot]@users.noreply.github.com>
@github-actions github-actions bot added the locked label Nov 7, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Nov 7, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants