-
-
Notifications
You must be signed in to change notification settings - Fork 4k
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: rename internal object properties #9532
Conversation
🦋 Changeset detectedLatest commit: 7599969 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
chore: rename internal object properties order properties and add comments add missing remove_in_transitions
61ff5ff
to
da1e994
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sad that this is necessary, but it is
Is it? For 4ms? And 0.7kb? I don't think it is. Svelte 5 is in JS instead of TS so jump-to-definition makes sense. For the developer experience. This undoes that, no? |
@sisou Those are pretty big figures for a hello world SvelteKit app that starts at 9kb. |
This changes all our internal object properties to single characters. This improves code-size, parse time and also improves runtime performance across the board. It just makes the coder harder to read, so I've added comments throughout that labels what they are in most cases. I've likely missed some obvious ones though as there's so many properties going on here.
This saves 0.7kb min+gzip and improves parse time on the default SvelteKit app startup by 4ms!