You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi community, we recently updated our models' mlc-chat-config.json on hugging face to use the latest conversation template. The goal is to make templates more lightweight, hence not requiring an npm bump whenever we support a new model (credit to @rickzx).
If you are not using npm ^0.2.29, you might encounter an issue complaining about an unrecognized conversation template, which can be solved by updating the web-llm npm.
We apologize for the breaking changes. It is possible that we would introduce other breaking changes this week in preparation for a new release of WebLLM.
After the new release (in ~1 week), things should stabilize and we will try our best to mitigate such breaking changes (i.e. not requiring updates of npm). We will also introduce wasm versioning so that npm version can pair with wasm version.
Thank you for your understanding!
The text was updated successfully, but these errors were encountered:
Hi community, we recently updated our models'
mlc-chat-config.json
on hugging face to use the latest conversation template. The goal is to make templates more lightweight, hence not requiring an npm bump whenever we support a new model (credit to @rickzx).If you are not using npm
^0.2.29
, you might encounter an issue complaining about an unrecognized conversation template, which can be solved by updating the web-llm npm.We apologize for the breaking changes. It is possible that we would introduce other breaking changes this week in preparation for a new release of WebLLM.
After the new release (in ~1 week), things should stabilize and we will try our best to mitigate such breaking changes (i.e. not requiring updates of npm). We will also introduce wasm versioning so that npm version can pair with wasm version.
Thank you for your understanding!
The text was updated successfully, but these errors were encountered: