-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Split swc_core/allocator_node out of __swc_core_binding_napi #3772
Merged
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
The latest updates on your projects. Learn more about Vercel for Git ↗︎
8 Ignored Deployments
|
Brooooooklyn
force-pushed
the
split-allocator-out
branch
from
February 13, 2023 16:20
286a6b5
to
47d598f
Compare
|
This was referenced Feb 13, 2023
Benchmark for f0c0f13
Click to view full benchmark
|
sokra
approved these changes
Feb 13, 2023
Brooooooklyn
added
pr: automerge
Kodiak will merge these automatically after checks pass
and removed
pr: automerge
Kodiak will merge these automatically after checks pass
labels
Feb 14, 2023
Brooooooklyn
added a commit
to swc-project/swc
that referenced
this pull request
Feb 14, 2023
Brooooooklyn
added
the
pr: automerge
Kodiak will merge these automatically after checks pass
label
Feb 14, 2023
Benchmark for 889e86f
Click to view full benchmark
|
timneutkens
pushed a commit
to vercel/next.js
that referenced
this pull request
Feb 14, 2023
The `experimental.turbotrace.memoryLimit` is not actually working, we need to use `turbo_malloc` as the global allocator to make it work. ~~Block by:~~ - swc-project/swc#6940 - vercel/turborepo#3772 ## This PR also upgrades `turbopack-230213.2` to `turbopack-230214.1` - vercel/turborepo#3767 - vercel/turborepo#3772 - vercel/turborepo#3762 - vercel/turborepo#3741 - vercel/turborepo#3796
jridgewell
pushed a commit
to vercel/next.js
that referenced
this pull request
Mar 10, 2023
…turborepo#3772) We only can use `turbo_malloc` in `next.js` without `swc_node_base` included
sokra
pushed a commit
to vercel/next.js
that referenced
this pull request
Mar 13, 2023
…turborepo#3772) We only can use `turbo_malloc` in `next.js` without `swc_node_base` included
ForsakenHarmony
pushed a commit
to vercel/next.js
that referenced
this pull request
Jul 25, 2024
…turborepo#3772) We only can use `turbo_malloc` in `next.js` without `swc_node_base` included
ForsakenHarmony
pushed a commit
to vercel/next.js
that referenced
this pull request
Jul 29, 2024
…turborepo#3772) We only can use `turbo_malloc` in `next.js` without `swc_node_base` included
ForsakenHarmony
pushed a commit
to vercel/next.js
that referenced
this pull request
Aug 1, 2024
…turborepo#3772) We only can use `turbo_malloc` in `next.js` without `swc_node_base` included
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
We only can use
turbo_malloc
innext.js
withoutswc_node_base
included