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

chore(swc_nodejs_common): remove swc_node_base from swc_nodejs_common #6940

Merged
merged 1 commit into from
Feb 14, 2023

Conversation

Brooooooklyn
Copy link
Member

Copy link
Member

@kdy1 kdy1 left a comment

Choose a reason for hiding this comment

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

swc-bump:

  • swc_nodejs_common

@kdy1 kdy1 added this to the Planned milestone Feb 14, 2023
@Brooooooklyn Brooooooklyn merged commit 0771418 into main Feb 14, 2023
@Brooooooklyn Brooooooklyn deleted the remove-allocator-from-nodejs_common branch February 14, 2023 03:13
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
@kdy1 kdy1 modified the milestones: Planned, v1.3.36 Feb 21, 2023
@swc-project swc-project locked as resolved and limited conversation to collaborators Mar 23, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants