-
Notifications
You must be signed in to change notification settings - Fork 27k
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
chore(next/image)!: mark onLoadingComplete
as deprecated in favor of onLoad
#56944
Merged
kodiakhq
merged 7 commits into
canary
from
styfle/next-1688-mark-onloadingcomplete-as-deprecated
Oct 17, 2023
Merged
chore(next/image)!: mark onLoadingComplete
as deprecated in favor of onLoad
#56944
kodiakhq
merged 7 commits into
canary
from
styfle/next-1688-mark-onloadingcomplete-as-deprecated
Oct 17, 2023
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ijjk
added
area: documentation
examples
Issue/PR related to examples
created-by: Next.js team
PRs by the Next.js team.
type: next
labels
Oct 17, 2023
Stats from current PRDefault BuildGeneral Overall increase
|
vercel/next.js canary | vercel/next.js styfle/next-1688-mark-onloadingcomplete-as-deprecated | Change | |
---|---|---|---|
buildDuration | 10.3s | 10.4s | |
buildDurationCached | 6.1s | 6.2s | N/A |
nodeModulesSize | 174 MB | 174 MB | |
nextStartRea..uration (ms) | 527ms | 534ms | N/A |
Client Bundles (main, webpack)
vercel/next.js canary | vercel/next.js styfle/next-1688-mark-onloadingcomplete-as-deprecated | Change | |
---|---|---|---|
199-HASH.js gzip | 27.5 kB | 27.5 kB | ✓ |
3f784ff6-HASH.js gzip | 53.1 kB | 53.1 kB | ✓ |
99.HASH.js gzip | 182 B | 182 B | ✓ |
framework-HASH.js gzip | 45.3 kB | 45.3 kB | ✓ |
main-app-HASH.js gzip | 254 B | 251 B | N/A |
main-HASH.js gzip | 32.9 kB | 32.9 kB | N/A |
webpack-HASH.js gzip | 1.75 kB | 1.75 kB | N/A |
Overall change | 126 kB | 126 kB | ✓ |
Legacy Client Bundles (polyfills)
vercel/next.js canary | vercel/next.js styfle/next-1688-mark-onloadingcomplete-as-deprecated | Change | |
---|---|---|---|
polyfills-HASH.js gzip | 31 kB | 31 kB | ✓ |
Overall change | 31 kB | 31 kB | ✓ |
Client Pages
vercel/next.js canary | vercel/next.js styfle/next-1688-mark-onloadingcomplete-as-deprecated | 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.57 kB | 2.57 kB | N/A |
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.35 kB | 4.35 kB | N/A |
index-HASH.js gzip | 256 B | 256 B | ✓ |
link-HASH.js gzip | 2.64 kB | 2.63 kB | N/A |
routerDirect..HASH.js gzip | 312 B | 311 B | N/A |
script-HASH.js gzip | 385 B | 384 B | N/A |
withRouter-HASH.js gzip | 307 B | 308 B | N/A |
1afbb74e6ecf..834.css gzip | 106 B | 106 B | ✓ |
Overall change | 1.08 kB | 1.08 kB | ✓ |
Client Build Manifests
vercel/next.js canary | vercel/next.js styfle/next-1688-mark-onloadingcomplete-as-deprecated | Change | |
---|---|---|---|
_buildManifest.js gzip | 485 B | 482 B | N/A |
Overall change | 0 B | 0 B | ✓ |
Rendered Page Sizes
vercel/next.js canary | vercel/next.js styfle/next-1688-mark-onloadingcomplete-as-deprecated | Change | |
---|---|---|---|
index.html gzip | 528 B | 530 B | N/A |
link.html gzip | 541 B | 542 B | N/A |
withRouter.html gzip | 523 B | 524 B | N/A |
Overall change | 0 B | 0 B | ✓ |
Edge SSR bundle Size
vercel/next.js canary | vercel/next.js styfle/next-1688-mark-onloadingcomplete-as-deprecated | Change | |
---|---|---|---|
edge-ssr.js gzip | 93.6 kB | 93.6 kB | N/A |
page.js gzip | 154 kB | 154 kB | N/A |
Overall change | 0 B | 0 B | ✓ |
Middleware size
vercel/next.js canary | vercel/next.js styfle/next-1688-mark-onloadingcomplete-as-deprecated | Change | |
---|---|---|---|
middleware-b..fest.js gzip | 626 B | 623 B | N/A |
middleware-r..fest.js gzip | 150 B | 151 B | N/A |
middleware.js gzip | 22.5 kB | 22.5 kB | N/A |
edge-runtime..pack.js gzip | 1.92 kB | 1.92 kB | ✓ |
Overall change | 1.92 kB | 1.92 kB | ✓ |
Tests Passed |
styfle
requested review from
timneutkens,
ijjk,
shuding,
huozhi,
ztanner and
a team
as code owners
October 17, 2023 15:40
styfle
requested review from
jh3y and
steven-tey
and removed request for
a team
October 17, 2023 15:40
jh3y
previously approved these changes
Oct 17, 2023
Allow CI Workflow Run
Note: this should only be enabled once the PR is ready to go and can only be enabled by a maintainer |
1 similar comment
Allow CI Workflow Run
Note: this should only be enabled once the PR is ready to go and can only be enabled by a maintainer |
ijjk
approved these changes
Oct 17, 2023
kodiakhq
bot
deleted the
styfle/next-1688-mark-onloadingcomplete-as-deprecated
branch
October 17, 2023 21:12
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
CI approved
Approve running CI for fork
created-by: Next.js team
PRs by the Next.js team.
examples
Issue/PR related to examples
locked
type: next
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
History
We used to pass
onLoad
through directly to the underlying img soonLoadingComplete
was introduced in order to handle the case whenplaceholder="blur"
was used andonLoad
would trigger before the placeholder was removed.We have since changed the behavior of
onLoad
so that it acts the same asonLoadingComplete
and thereforeonLoadingComplete
is no longer needed.What is this PR doing?
This PR marks
onLoadingComplete
as deprecated in favor ofonLoad
. In the future, we may removeonLoadingComplete
.