From fb6a004f12cf08bbcbe0e796f916f8f4ae62072e Mon Sep 17 00:00:00 2001 From: bracesproul Date: Wed, 31 Jul 2024 12:57:00 -0700 Subject: [PATCH] docs[patch]: Fix import path in dispatching events doc --- docs/core_docs/docs/how_to/callbacks_custom_events.ipynb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/core_docs/docs/how_to/callbacks_custom_events.ipynb b/docs/core_docs/docs/how_to/callbacks_custom_events.ipynb index bd345828c147..effe80810b02 100644 --- a/docs/core_docs/docs/how_to/callbacks_custom_events.ipynb +++ b/docs/core_docs/docs/how_to/callbacks_custom_events.ipynb @@ -46,7 +46,7 @@ ":::caution Compatibility\n", "Dispatching custom callback events requires `@langchain/core>=0.2.16`. See [this guide](/docs/how_to/installation/#installing-integration-packages) for some considerations to take when upgrading `@langchain/core`.\n", "\n", - "The default entrypoint below triggers an import and initialization of [`async_hooks`](https://nodejs.org/api/async_hooks.html) to enable automatic `RunnableConfig` passing, which is not supported in all environments. If you see import issues, you must import from `@langchain/callbacks/dispatch/web` and propagate the `RunnableConfig` object manually (see example below).\n", + "The default entrypoint below triggers an import and initialization of [`async_hooks`](https://nodejs.org/api/async_hooks.html) to enable automatic `RunnableConfig` passing, which is not supported in all environments. If you see import issues, you must import from `@langchain/core/callbacks/dispatch/web` and propagate the `RunnableConfig` object manually (see example below).\n", ":::\n", "```" ]