fix(adk): fix lodash ESM import for Node 22

[Kotchanit]

Hi! 👋

Firstly, thanks for your work on this project! 🙂

Today I used patch-package to patch @google/adk@0.2.2 for the project I'm working on.

Here is the diff that solved my problem:

diff --git a/node_modules/@google/adk/dist/esm/agents/llm_agent.js b/node_modules/@google/adk/dist/esm/agents/llm_agent.js
index a73f981..297576e 100644
--- a/node_modules/@google/adk/dist/esm/agents/llm_agent.js
+++ b/node_modules/@google/adk/dist/esm/agents/llm_agent.js
@@ -3,7 +3,7 @@
  * Copyright 2025 Google LLC
  * SPDX-License-Identifier: Apache-2.0
  */
-import { cloneDeep } from "lodash";
+import _ from "lodash";
 import { z } from "zod";
 import { BaseCodeExecutor } from "../code_executors/base_code_executor.js";
 import { BuiltInCodeExecutor } from "../code_executors/built_in_code_executor.js";
@@ -452,7 +452,7 @@ async function* runPreProcessor(invocationContext, llmRequest) {
         buildExecutableCodePart(codeStr)
       ]
     };
-    llmRequest.contents.push(cloneDeep(codeContent));
+    llmRequest.contents.push(_.cloneDeep(codeContent));
     yield createEvent({
       invocationId: invocationContext.invocationId,
       author: agent.name,
@@ -481,7 +481,7 @@ async function* runPreProcessor(invocationContext, llmRequest) {
       codeExecutionResult
     );
     yield executionResultEvent;
-    llmRequest.contents.push(cloneDeep(executionResultEvent.content));
+    llmRequest.contents.push(_.cloneDeep(executionResultEvent.content));
   }
 }
 async function* runPostProcessor(invocationContext, llmResponse) {

This issue body was partially generated by patch-package.

[kalenkevich]

Hello, thanks for the issue.

Related to #59

[kalenkevich]

Fixed in cf8cf9f

[Kotchanit]

@kalenkevich Thanks for the update!
Is there an estimated timeline for when the next npm release might happen?

[ScottMansfield]

We will be pushing a patch release today

[ScottMansfield]

v0.2.3 has been released, can you try it and see if it fixes your build without your patch?

[kalenkevich]

Hello, just submitted another fix for that and published new version. Could you please install @google/adk 0.2.4 verify that it works fine, many thanks!

[rickardrosen]

Lodash dep took me by surprise and broke deno integration. I don’t think there’s been a release for about a decade, and we have newer and more slimmed down ES6 alternatives these days.

Or just a bit of recursion…

I might be missing some details here, but have personally not reached for lodash in years.

I’m sure there’s good reason, but I’m curious.

[kalenkevich]

@rickardrosen Lodash has been widely used as an industry-standard utility library for many years. We are now using lodash-es, which supports tree-shaking for bundlers and full ESM compatibility while still being a very powerful utility library. That is the main reason for our choice.

However, we are always open to good suggestions and alternatives that can improve the project. Do you have any recommendations for replacing Lodash? Thanks!

[rickardrosen]

I guess I wouldn’t have noticed unless for the fact that it broke deno. I’ve worked with deno for quite while and this is obviously the first time a dep I rely on uses lodash - otherwise I’d have seen this breakage before.

In the referenced code I see objects being cloned and personally, for this specific task I’d look to use: structuredClone

Should work for both node & deno runtimes.

I haven’t dived in to the ADK details, but lodash feels like something from a bygone era, for me personally. But it’s also like meeting an old friend you haven’t seen for ages. :)

[Kotchanit]

v0.2.3 has been released, can you try it and see if it fixes your build without your patch?

Just tried v2.0.4 and it works fine on my end without the patch. Thanks!