Issue with data-provider during build - src/web.ts - error TS2322

[JulianHandrup]

Hello,

I'm suddenly having problems building the image myself.
It worked fine until it didn't anymore...

The issue I'm getting is displayed below and is about type incompatibility in "src/web.ts".
I have not changed this part and it also does not build the main branch (only adjusted by setting proxy in Dockerfile).
Did anyone experience his or similar behaviour during the build via docker build -f Dockerfile?

Error:

> [email protected] clean
> rimraf dist

(plugin rpt2) RollupError: [plugin rpt2] src/web.ts - error TS2322: Type '{ safeSearch: SafeSearchTypes; jinaApiKey: string; cohereApiKey: string; serperApiKey: string; firecrawlApiKey: string; firecrawlApiUrl: string; searxngInstanceUrl?: string | undefined; ... 5 more ...; firecrawlOptions?: { ...; } | undefined; }' is not assignable to type '{ serperApiKey: string; searxngInstanceUrl: string; searxngApiKey: string; firecrawlApiKey: string; firecrawlApiUrl: string; jinaApiKey: string; cohereApiKey: string; safeSearch: SafeSearchTypes; ... 4 more ...; firecrawlOptions?: { ...; } | undefined; }'.
  Types of property 'searxngInstanceUrl' are incompatible.
    Type 'string | undefined' is not assignable to type 'string'.
      Type 'undefined' is not assignable to type 'string'.

Jenkins-Command:

sudo docker build --no-cache --build-arg HTTP_PROXY="${PROXY}" --build-arg HTTPS_PROXY="${PROXY}" -f Dockerfile -t my-librechat:${target} .

Dockerfile:

# v0.7.9

# Base node image
FROM node:20-alpine AS node

ARG HTTP_PROXY
ARG HTTPS_PROXY

# Install jemalloc
RUN export http_proxy=$HTTP_PROXY; export https_proxy=$HTTPS_PROXY ; apk add --no-cache jemalloc
RUN export http_proxy=$HTTP_PROXY; export https_proxy=$HTTPS_PROXY ; apk add --no-cache python3 py3-pip uv

# Set environment variable to use jemalloc
ENV LD_PRELOAD=/usr/lib/libjemalloc.so.2

# Add `uv` for extended MCP support
COPY --from=ghcr.io/astral-sh/uv:0.6.13 /uv /uvx /bin/
RUN uv --version
RUN node -v

RUN mkdir -p /app && chown node:node /app
WORKDIR /app

USER node

COPY --chown=node:node . .

RUN npm config set proxy $HTTP_PROXY ; \
    npm config set https-proxy $HTTPS_PROXY;


RUN \
    # Allow mounting of these files, which have no default
    touch .env ; \
    # Create directories for the volumes to inherit the correct permissions
    mkdir -p /app/client/public/images /app/api/logs ; \
    npm config set fetch-retry-maxtimeout 90000 ; \
    npm config set fetch-retries 3 ; \
    npm config set fetch-retry-mintimeout 15000 ; \
    npm install --force --no-audit; \
    # React client build
    NODE_OPTIONS="--max-old-space-size=2048" npm run frontend; \
    npm prune --production; \
    npm cache clean --force


RUN mkdir -p /app/client/public/images /app/api/logs

RUN npm config rm proxy; \
	npm config rm https-proxy;

# Node API setup
EXPOSE 3080
ENV HOST=0.0.0.0
CMD ["npm", "run", "backend"]

# Optional: for client with nginx routing
# FROM nginx:stable-alpine AS nginx-client
# WORKDIR /usr/share/nginx/html
# COPY --from=node /app/client/dist /usr/share/nginx/html
# COPY client/nginx.conf /etc/nginx/conf.d/default.conf
# ENTRYPOINT ["nginx", "-g", "daemon off;"]

Please note that without npm install --force I get this error:

npm error While resolving: [email protected]
npm error Found: [email protected]
npm error node_modules/keyv
npm error   keyv@"^5.3.2" from @keyv/[email protected]
npm error   api/node_modules/@keyv/redis
npm error     @keyv/redis@"^4.3.3" from @librechat/[email protected]
npm error     api
npm error       @librechat/[email protected]
npm error       node_modules/@librechat/backend
npm error         workspace api from the root project
npm error   peer keyv@"^5.3.2" from @librechat/[email protected]
npm error   packages/api
npm error     @librechat/[email protected]
npm error     node_modules/@librechat/api
npm error       workspace packages/api from the root project
npm error       1 more (@librechat/backend)
npm error   1 more (@librechat/backend)
npm error
npm error Could not resolve dependency:
npm error peer keyv@"^4.5.4" from [email protected]
npm error packages/mcp
npm error   [email protected]
npm error   node_modules/librechat-mcp
npm error     workspace packages/mcp from the root project
npm error
npm error Conflicting peer dependency: [email protected]
npm error node_modules/keyv
npm error   peer keyv@"^4.5.4" from [email protected]
npm error   packages/mcp
npm error     [email protected]
npm error     node_modules/librechat-mcp
npm error       workspace packages/mcp from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.

I've tried a lot of stuff already, I remove existing docker-images before build, the jenkins workspace is cleared before and after builds, etc. but I'm out of ideas.
And I'm not comfortable enough with TypeScript etc to debug or see if this is an actual issue or if there's something wrong with my environment. Because clearly, if there was an issue with the build, it would have popped up by now.

So, if anyone has a solution or ideas of what else I could try, then please, let me know.
It would already help a little to know that it's not a bug in the code but rather a hickup in my build / env.

[danny-avila]

The TypeScript error suggests the searxngInstanceUrl property is expected to be required (string) but is being passed as optional (string | undefined). This type mismatch is likely due to outdated type definitions from the older version you're using.

I would suggest pulling the latest changes since I can see on your dockerfile, it mentions v0.7.9, it should now be v0.8.0-rc1.

Docker builds are completing successfully in the CI environment as well as locally for me (using official Dockerfile):
https://github.com/danny-avila/LibreChat/actions/runs/16732310949/job/47363045000

The only other difference I see is the use of proxy and npm install --force which you should not use.

It's possible one of the packages is not resolving correctly based on your build environment (CPU architecture), but try the above first.

[JulianHandrup]

Thanks for your time and input.
The solution was quite simple, but without actual access to the build server quite hard to find out for me..

The Jenkins server connected to the actual build server, transfered files and executed the bash script there - but did not once clean up afterwards. That meant that there was an ancient package "mcp" under {root}/packages which after some time finally bit me in the a** and caused some package incompatibilities and incorrect type definitions.

So, lesson learned, always keep a clean build env.