I'm getting this Error [ERR_PACKAGE_PATH_NOT_EXPORTED]: Package subpath './dist/tools/json' is not defined by "exports" in node_modules\langchain\package.json (working with typescript code)

[sapana-k]

Checked other resources

• I added a very descriptive title to this question.
• I searched the LangChain documentation with the integrated search.
• I used the GitHub search to find a similar question and didn't find it.

Commit to Help

• I commit to help with one of those options 👆

Example Code

import { JsonSpec } from "langchain/dist/tools/json";
import fs from "fs";
const jsonData = fs.readFileSync('events.json', 'utf-8');
const data = JSON.parse(jsonData);
const json_spec = new JsonSpec(data);

Description

I'm trying to use JsonSpec but it is causing [ERR_PACKAGE_PATH_NOT_EXPORTED]: Package subpath './dist/tools/json' is not defined by "exports" in node_modules\langchain\package.json

System Info

Node.js v21.6.1
"langchain": "^0.1.28"

[dosubot[bot]]

Based on the error message you're encountering, it seems like you're trying to import JsonSpec from a subpath (./dist/tools/json) that is not explicitly defined in the exports field of the langchain package's package.json file. The exports field controls which files are accessible to consumers of the package, and if a file or subpath is not defined there, it cannot be imported directly when using ES modules or certain Node.js versions that enforce these export maps.

There are a few potential solutions to this issue:

1. Check for Alternative Import Paths: The langchain package might offer an alternative way to import or access the functionality you need from ./dist/tools/json. Check the package's documentation or source code to see if there's another way to import JsonSpec.

2. Contact the Package Maintainers: If there's no alternative import path, you might need to reach out to the maintainers of the langchain package to report this issue. It's possible they need to update their package to include the missing export.

3. Fork and Modify: If you need an immediate resolution, you could fork the langchain repository, add the necessary export path to the package.json, and then use your forked version. However, this approach means you'll need to maintain your fork and merge updates from the original repository.

4. Local Patching: For a temporary workaround, you might consider patching the package locally using tools like patch-package, which allows you to keep modifications in your project repository. This doesn't solve the problem at its root but can unblock development.

I found a few similar issues in the LangChain JS repository that might be helpful:

• Getting [ERR_PACKAGE_PATH_NOT_EXPORTED] on execution
• Package.json import issues
• Error [ERR_PACKAGE_PATH_NOT_EXPORTED]: Package subpath './dist/prompts'

These issues suggest that updating the langchain package to the latest version or ensuring that you're using the correct version might help resolve the issue. Additionally, you might need to update your project setup to use the CommonJS module system, as suggested in the Package.json import issues issue.

I hope this helps! If you have any other questions or need further clarification, feel free to ask.

Sources

• Getting [ERR_PACKAGE_PATH_NOT_EXPORTED] on execution
• Package.json import issues
• Error [ERR_PACKAGE_PATH_NOT_EXPORTED]: Package subpath './dist/prompts'
• Package subpath './weaviate' is not defined by "exports"
• Having Error [ERR_PACKAGE_PATH_NOT_EXPORTED]
• Typescript not working
• langchain/package.json

About Dosu

This response is meant to be useful and save you time. It is not meant to be a precise solution, but rather a starting point for your own research.

Help me be more useful! Please leave a 👍 if this is helpful and 👎 if it is irrelevant.

If you want to continue the conversation, start your reply with @dosu-bot.