Skip to content

fix: concat performance#422

Draft
styfle wants to merge 3 commits intomainfrom
fix-issue-314
Draft

fix: concat performance#422
styfle wants to merge 3 commits intomainfrom
fix-issue-314

Conversation

@styfle
Copy link
Member

@styfle styfle commented Jun 3, 2024

}
return value;
};
export function safeStringify(obj: unknown) {
Copy link
Member Author

Choose a reason for hiding this comment

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

We need a more comprehensive stringify to handle all possible inputs

type Walk = (node: Node) => Promise<EvaluatedValue>;
type State = { computeBranches: boolean; vars: Record<string, any> };

const walkCache = new Map<string, EvaluatedValue>();
Copy link
Member Author

Choose a reason for hiding this comment

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

We should probably use a LRU cache to avoid running out of memory. Right now, the number of entries is unbounded.

@ojj1123
Copy link

ojj1123 commented Jul 4, 2024

Is this PR also related with vercel/next.js#65512 ?

thanks for reporting, we identified it to an issue with node-file-trace, but we're still unsure why concat messes with it

vercel/next.js#65512 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Many chained concat() calls can cause trace to fail

2 participants