Cannot find module 'librechat-data-provider' #7416

ddanieli · 2025-05-16T07:04:16Z

ddanieli
May 16, 2025

What happened?

I'm following instructions here:

https://www.librechat.ai/docs/local/npm

Expected:

To launch both frontend and backend servers.

Version Information

% git rev-parse HEAD
2a3bf25

Steps to Reproduce

Followed instructions from https://www.librechat.ai/docs/local/npm.

Repro (Mac Sequoia 15.4.1/Node v20.17.0/npm v11.4.0):

Last login: Fri May 16 08:56:36 on ttys061
Now using node v20.17.0 (npm v11.4.0)
damondanieli@Damons-MacBook-Air danny-avila % git clone https://github.com/danny-avila/LibreChat
Cloning into 'LibreChat'...
remote: Enumerating objects: 46117, done.
remote: Counting objects: 100% (108/108), done.
remote: Compressing objects: 100% (75/75), done.
remote: Total 46117 (delta 69), reused 33 (delta 33), pack-reused 46009 (from 3)
Receiving objects: 100% (46117/46117), 81.24 MiB | 10.48 MiB/s, done.
Resolving deltas: 100% (33519/33519), done.
damondanieli@Damons-MacBook-Air danny-avila % cd LibreChat/
damondanieli@Damons-MacBook-Air LibreChat % cp .env.example .env
damondanieli@Damons-MacBook-Air LibreChat % npm ci
npm warn deprecated @types/[email protected]: This is a stub types definition. winston provides its own type definitions, so you do not need this installed.
npm warn deprecated @humanwhocodes/[email protected]: Use @eslint/config-array instead
npm warn deprecated [email protected]: Use your platform's native atob() and btoa() methods instead
npm warn deprecated @humanwhocodes/[email protected]: Use @eslint/object-schema instead
npm warn deprecated [email protected]: Glob versions prior to v9 are no longer supported
npm warn deprecated [email protected]: Use your platform's native DOMException instead
npm warn deprecated [email protected]: Please use @jridgewell/sourcemap-codec instead
npm warn deprecated [email protected]: This package has been decomissioned. See https://github.com/ldapjs/node-ldapjs/blob/8ffd0bc9c149088a10ec4c1ec6a18450f76ad05d/README.md
npm warn deprecated [email protected]: This version is no longer supported. Please see https://eslint.org/version-support for other options.
npm warn deprecated [email protected]: This version is no longer supported. Please see https://eslint.org/version-support for other options.

added 3217 packages, and audited 3224 packages in 28s

516 packages are looking for funding
  run `npm fund` for details

found 0 vulnerabilities
damondanieli@Damons-MacBook-Air LibreChat % npm run frontend

> [email protected] frontend
> npm run build:data-provider && npm run build:mcp && npm run build:data-schemas && cd client && npm run build


> [email protected] build:data-provider
> cd packages/data-provider && npm run build


> [email protected] build
> npm run clean && rollup -c --silent --bundleConfigAsCjs


> [email protected] clean
> rimraf dist


> [email protected] build:mcp
> cd packages/mcp && npm run build


> [email protected] build
> npm run clean && rollup -c --bundleConfigAsCjs


> [email protected] clean
> rimraf dist


src/index.ts → dist/index.js...
(!) [plugin typescript] src/manager.ts (3:49): @rollup/plugin-typescript TS2307: Cannot find module 'librechat-data-provider' or its corresponding type declarations.
/Users/damondanieli/go/src/github.com/danny-avila/LibreChat/packages/mcp/src/manager.ts:3:49

3 import type { JsonSchemaType, MCPOptions } from 'librechat-data-provider';
                                                  ~~~~~~~~~~~~~~~~~~~~~~~~~

(!) [plugin typescript] src/types/mcp.ts (9:8): @rollup/plugin-typescript TS2307: Cannot find module 'librechat-data-provider' or its corresponding type declarations.
/Users/damondanieli/go/src/github.com/danny-avila/LibreChat/packages/mcp/src/types/mcp.ts:9:8

9 } from 'librechat-data-provider';
         ~~~~~~~~~~~~~~~~~~~~~~~~~

(!) [plugin typescript] src/types/mcp.ts (10:46): @rollup/plugin-typescript TS2307: Cannot find module 'librechat-data-provider' or its corresponding type declarations.
/Users/damondanieli/go/src/github.com/danny-avila/LibreChat/packages/mcp/src/types/mcp.ts:10:46

10 import type { JsonSchemaType, TPlugin } from 'librechat-data-provider';
                                                ~~~~~~~~~~~~~~~~~~~~~~~~~

(!) [plugin node-resolve] Could not resolve import "pkce-challenge" in /Users/damondanieli/go/src/github.com/danny-avila/LibreChat/node_modules/@modelcontextprotocol/sdk/dist/esm/client/auth.js using exports defined in /Users/damondanieli/go/src/github.com/danny-avila/LibreChat/node_modules/pkce-challenge/package.json.
(!) Unresolved dependencies
https://rollupjs.org/troubleshooting/#warning-treating-module-as-external-dependency
pkce-challenge (imported by "../../node_modules/@modelcontextprotocol/sdk/dist/esm/client/auth.js")
created dist/index.js in 2.5s

> [email protected] build:data-schemas
> cd packages/data-schemas && npm run build


> @librechat/[email protected] build
> npm run clean && rollup -c --silent --bundleConfigAsCjs


> @librechat/[email protected] clean
> rimraf dist


> @librechat/[email protected] build
> cross-env NODE_ENV=production vite build

vite v6.3.4 building for production...
✓ 221 modules transformed.
transforming (2647) ../node_modules/lucide-react/dist/esm/icons/user-search.js
PWA v0.21.2
mode      generateSW
precache  49 entries (0.00 KiB)
files generated
  dist/sw.js
  dist/workbox-4c320e2c.js
warnings
  One of the glob patterns doesn't match any files. Please remove or fix the following: {
  "globDirectory": "/Users/damondanieli/go/src/github.com/danny-avila/LibreChat/client/dist",
  "globPattern": "**/*",
  "globIgnores": [
    "images/**/*",
    "sw.js",
    "workbox-*.js"
  ]
}

✗ Build failed in 4.32s
error during build:
[vite-plugin-pwa:build] [plugin vite-plugin-pwa:build] There was an error during the build:
  [vite]: Rollup failed to resolve import "librechat-data-provider" from "/Users/damondanieli/go/src/github.com/danny-avila/LibreChat/client/src/hooks/AuthContext.tsx".
This is most likely unintended because it can break your application at runtime.
If you do want to externalize this module explicitly add it to
`build.rollupOptions.external`
Additionally, handling the error in the 'buildEnd' hook caused the following error:
  [vite]: Rollup failed to resolve import "librechat-data-provider" from "/Users/damondanieli/go/src/github.com/danny-avila/LibreChat/client/src/hooks/AuthContext.tsx".
This is most likely unintended because it can break your application at runtime.
If you do want to externalize this module explicitly add it to
`build.rollupOptions.external`
    at getRollupError (file:///Users/damondanieli/go/src/github.com/danny-avila/LibreChat/node_modules/rollup/dist/es/shared/parseAst.js:397:41)
    at file:///Users/damondanieli/go/src/github.com/danny-avila/LibreChat/node_modules/rollup/dist/es/shared/node-entry.js:22876:39
    at async catchUnfinishedHookActions (file:///Users/damondanieli/go/src/github.com/danny-avila/LibreChat/node_modules/rollup/dist/es/shared/node-entry.js:22330:16)
    at async rollupInternal (file:///Users/damondanieli/go/src/github.com/danny-avila/LibreChat/node_modules/rollup/dist/es/shared/node-entry.js:22859:5)
    at async buildEnvironment (file:///Users/damondanieli/go/src/github.com/danny-avila/LibreChat/node_modules/vite/dist/node/chunks/dep-Bn81Esdm.js:46206:14)
    at async Object.defaultBuildApp [as buildApp] (file:///Users/damondanieli/go/src/github.com/danny-avila/LibreChat/node_modules/vite/dist/node/chunks/dep-Bn81Esdm.js:46684:5)
    at async CAC.<anonymous> (file:///Users/damondanieli/go/src/github.com/danny-avila/LibreChat/node_modules/vite/dist/node/cli.js:863:7)
npm error Lifecycle script `build` failed with error:
npm error code 1
npm error path /Users/damondanieli/go/src/github.com/danny-avila/LibreChat/client
npm error workspace @librechat/[email protected]
npm error location /Users/damondanieli/go/src/github.com/danny-avila/LibreChat/client
npm error command failed
npm error command sh -c cross-env NODE_ENV=production vite build
damondanieli@Damons-MacBook-Air LibreChat %

What browsers are you seeing the problem on?

No response

Relevant log output

n/a

Screenshots

No response

Code of Conduct

I agree to follow this project's Code of Conduct

ddanieli · 2025-05-16T07:07:22Z

ddanieli
May 16, 2025
Author

I've tried manually building the separate components with npm run build:data-provider && ..., npm run reinstall and using bun via npm run b:reinstall, manually linking the package into the directories as well as rolling back to v0.7.8 with the same results.

0 replies

danny-avila · 2025-05-16T12:52:22Z

danny-avila
May 16, 2025
Maintainer

Moved to troubleshooting since it can't be reproduced.

This build would also be failing: https://github.com/danny-avila/LibreChat/actions/runs/15056102530/job/42322263146

Try running what the commands do manually. Please note any errors at any step.

First, delete all node_modules directories already in the project, something like:

# haven't tested this
for dir in . ./packages/data-provider ./packages/data-schemas ./packages/mcp ./client ./api; do rm -rf "$dir/node_modules"; done

then clean cache

npm cache clean --force

Install packages

npm ci

Now run each package compile separately.

cd packages/data-provider && npm run build
cd packages/mcp && npm run build
cd packages/data-schemas && npm run build
cd client && npm run build

7 replies

kamaldua65 May 16, 2025

I had same issue, then i ran npm run frontend first to build and later npm run backend , then there was no issue

maxesse May 23, 2025

I also have this issue unfortunately, weirdly it just started happening.

It fails building mcp following the steps above:

 cd packages/mcp && npm run build
npm warn Unknown project config "always-auth". This will stop working in the next major version of npm.

> [email protected] build
> npm run clean && rollup -c --bundleConfigAsCjs

npm warn Unknown project config "always-auth". This will stop working in the next major version of npm.

> [email protected] clean
> rimraf dist


src/index.ts → dist/index.js...
(!) [plugin typescript] src/manager.ts (3:49): @rollup/plugin-typescript TS2307: Cannot find module 'librechat-data-provider' or its corresponding type declarations.
/Users/sannamass/Developer/LibreChat/packages/mcp/src/manager.ts:3:49

3 import type { JsonSchemaType, MCPOptions } from 'librechat-data-provider';
                                                  ~~~~~~~~~~~~~~~~~~~~~~~~~

(!) [plugin typescript] src/types/mcp.ts (9:8): @rollup/plugin-typescript TS2307: Cannot find module 'librechat-data-provider' or its corresponding type declarations.
/Users/sannamass/Developer/LibreChat/packages/mcp/src/types/mcp.ts:9:8

9 } from 'librechat-data-provider';
         ~~~~~~~~~~~~~~~~~~~~~~~~~

(!) [plugin typescript] src/types/mcp.ts (10:46): @rollup/plugin-typescript TS2307: Cannot find module 'librechat-data-provider' or its corresponding type declarations.
/Users/sannamass/Developer/LibreChat/packages/mcp/src/types/mcp.ts:10:46

10 import type { JsonSchemaType, TPlugin } from 'librechat-data-provider';
                                                ~~~~~~~~~~~~~~~~~~~~~~~~~

(!) [plugin node-resolve] Could not resolve import "pkce-challenge" in /Users/sannamass/Developer/LibreChat/node_modules/@modelcontextprotocol/sdk/dist/esm/client/auth.js using exports defined in /Users/sannamass/Developer/LibreChat/node_modules/pkce-challenge/package.json.
(!) Unresolved dependencies
https://rollupjs.org/troubleshooting/#warning-treating-module-as-external-dependency
pkce-challenge (imported by "../../node_modules/@modelcontextprotocol/sdk/dist/esm/client/auth.js")
created dist/index.js in 2.1s

layrfranca-hotmart May 26, 2025

Same thing here. I also experienced this suddenly. Just started happening. Weird.

maxesse May 26, 2025

@layrfranca-hotmart I fixed it - basically had to completely nuke my node install(s). I removed the homebrew version of node, nvm and all the versions of node I had, then started from a blank slate by reinstalling nvm, then node 20.19, then update npm to the latest, and finally npm run reinstall worked and it was all fine. Something got really corrupted in the innards of node at some point.

layrfranca-hotmart Jun 2, 2025

I also fixed my problem here, but without concrete answers. I also experienced that feeling "Something got really corrupted in the innards of node at some point.". In my case, the only solution found was to rollback to a previous working commit and reimplement the stuff I was implementing.

ddanieli · 2025-05-28T10:29:49Z

ddanieli
May 28, 2025
Author

I've completely remove node and reinstalled as @layrfranca-hotmart suggested and that did not fix it.

However, I ran npm run frontend first which built the librechat-data-provider component and that seemed to fix the error on my system.

1 reply

evandrocoan May 31, 2025

I've completely remove node and reinstalled as @layrfranca-hotmart suggested and that did not fix it.

However, I ran npm run frontend first which built the librechat-data-provider component and that seemed to fix the error on my system.

Thanks. This also fixed the issue for me.

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Uh oh!

Cannot find module 'librechat-data-provider' #7416

Uh oh!

{{title}}

Uh oh!

Replies: 3 comments 8 replies

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Select a reply

Uh oh!

Uh oh!

Cannot find module 'librechat-data-provider' #7416

Uh oh!

ddanieli May 16, 2025

What happened?

Version Information

Steps to Reproduce

What browsers are you seeing the problem on?

Relevant log output

Screenshots

Code of Conduct

Replies: 3 comments · 8 replies

Uh oh!

ddanieli May 16, 2025 Author

Uh oh!

danny-avila May 16, 2025 Maintainer

Uh oh!

kamaldua65 May 16, 2025

Uh oh!

maxesse May 23, 2025

Uh oh!

layrfranca-hotmart May 26, 2025

Uh oh!

maxesse May 26, 2025

Uh oh!

layrfranca-hotmart Jun 2, 2025

Uh oh!

ddanieli May 28, 2025 Author

Uh oh!

evandrocoan May 31, 2025

ddanieli
May 16, 2025

Replies: 3 comments 8 replies

ddanieli
May 16, 2025
Author

danny-avila
May 16, 2025
Maintainer

ddanieli
May 28, 2025
Author