Skip to content
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

perf: Do not allocate if visitors are not used #391

Merged
merged 16 commits into from
Jan 23, 2025
Merged

perf: Do not allocate if visitors are not used #391

merged 16 commits into from
Jan 23, 2025

Conversation

kdy1
Copy link
Member

@kdy1 kdy1 commented Jan 23, 2025

No description provided.

Copy link

changeset-bot bot commented Jan 23, 2025

⚠️ No Changeset found

Latest commit: 11f300f

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@kdy1 kdy1 enabled auto-merge (squash) January 23, 2025 16:38
@kdy1 kdy1 disabled auto-merge January 23, 2025 16:38
@kdy1 kdy1 changed the title perf: Do not allocate as much as possible where visitors are not used perf: Do not allocate if visitors are not used Jan 23, 2025
@kdy1 kdy1 enabled auto-merge (squash) January 23, 2025 16:38
@kdy1 kdy1 merged commit 5886faf into main Jan 23, 2025
9 checks passed
@kdy1 kdy1 deleted the kdy1/perf branch January 23, 2025 17:19
kdy1 added a commit to vercel/next.js that referenced this pull request Jan 23, 2025
### What?

Apply swc-project/plugins#391

### Why?

Those passes allocates too much even when they are not used.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

1 participant