WebLLM cannot load new models

[alexander-fischer]

Checked other resources

• I added a very descriptive title to this issue.
• I searched the LangChain.js documentation with the integrated search.
• I used the GitHub search to find a similar question and didn't find it.
• I am sure that this is a bug in LangChain.js rather than my code.
• The bug is not resolved by updating to the latest stable version of LangChain (or the specific integration package).

Example Code

import * as webllm from "@mlc-ai/web-llm"

const MODEL = "gemma-2-2b-it-q4f16_1-MLC"

private async loadLLM() {
const initProgressCallback = (report: webllm.InitProgressReport) => {
console.log(report.text)
}

const createdEngine = await webllm.CreateMLCEngine(MODEL, {
    initProgressCallback: initProgressCallback,
})
return createdEngine

}

Error Message and Stack Trace (if applicable)

Uncaught (in promise) Error: Failed to load model: No URL found for model ID "gemma-2-2b-it-q4f16_1-MLC". Please check if the model ID is correct and included in the model_list configuration.
at findModelRecord (index.js:7479:23)
at MLCEngine.eval (index.js:7481:33)
at Generator.next ()
at fulfilled (index.js:1279:56)Understand this error

Description

I use langchain.js together with @mlc-ai/web-llm. New models cannot be loaded because langchain-community package requires an old version of web-llm.

I would recommend to update the peerDependency to 0.2.62.

System Info

"@langchain/community": "^0.2.31"
"@langchain/langgraph": "^0.1.9"
"@mlc-ai/web-llm": "^0.2.46"

platform: Mac
node version: 22.4.1

[dosubot]

The issue with loading the model "gemma-2-2b-it-q4f16_1-MLC" is likely because this model ID is not listed in the available model records. You can check the list of available model records here: https://github.com/mlc-ai/web-llm/blob/main/src/config.ts ^[1].

Additionally, the current version of the @mlc-ai/web-llm package specified in the package.json file of the LangChain.js repository is 0.2.46 ^[2]. If you believe that updating to a newer version (e.g., 0.2.62) would resolve the issue, you might consider updating the dependency in your project. However, ensure that the model ID you are trying to use is supported in the newer version.

To continue talking to Dosu, mention @dosu.