[Log] Set log level using 'loglevel' package #427
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
CharlieFRuan
added a commit
that referenced
this pull request
May 30, 2024
### Changes Main changes include: - New prebuilt models: - Phi3-mini - StableLM-2-zephyr-1.6B - Qwen1.5-1.8B - Hermes2-Pro-Llama-3-8B to prebuilt models - Updates on `ModelRecord` fields - For detail see: #435 - Update all WASMs - For detail see: #433 - Update all WASMs to v0.2.39 - Support grammar for Llama3, hence update examples/json-mode to use `Llama3` and `Hermes2-pro-Llama3-8B` for function calling in `examples/json-schema` - Use `loglevel` package: - For details see #427 - Fix `index.js.map` issue for Vite - #420 - Enhance error handling and ServiceWorker ### TVMjs TVMjs compiled at apache/tvm@71f7af7 - Main changes include: - apache/tvm#17031 - apache/tvm#17028 - apache/tvm#17021 ### WASM version - All wasms updated to 0.2.39 via mlc-ai/binary-mlc-llm-libs#123 for new MLC-LLM runtime (mainly grammar)
CharlieFRuan
pushed a commit
that referenced
this pull request
May 31, 2024
Follow up from #427 to prevent the following type issue introduced on `v0.2.39`: <img width="1328" alt="image" src="https://github.com/mlc-ai/web-llm/assets/418083/3b2d028f-71af-4e77-a779-e4176225b92a"> This issue fails type-checking [[reference](https://github.com/felladrin/MiniSearch/actions/runs/9298738476/job/25591213310?pr=356)] and forces users to define the `logLevel` config. But in fact, `logLevel` already has a default value and was intended to be an optional parameter. This PR fixes it.
jingyi-zhao-01
pushed a commit
to jingyi-zhao-01/web-llm
that referenced
this pull request
Dec 8, 2024
This PR introduces a new package, `logLevel`, which is a lightweight logging javascript library for managing logging levels and filtering debug logs in production. https://github.com/pimterry/loglevel We exposed `logLevel` as part of the engine config to allow users to modify it. The default log level is `WARN`. In `TRACE` level: <img width="766" alt="Screenshot 2024-05-26 at 6 45 43 PM" src="https://github.com/mlc-ai/web-llm/assets/23090573/1245d868-4848-4310-a4ed-b3097b0972cd"> In `WARN` level: <img width="779" alt="Screenshot 2024-05-26 at 6 53 27 PM" src="https://github.com/mlc-ai/web-llm/assets/23090573/0a391d55-5d40-4199-bb2b-7c02600b2460">
jingyi-zhao-01
pushed a commit
to jingyi-zhao-01/web-llm
that referenced
this pull request
Dec 8, 2024
### Changes Main changes include: - New prebuilt models: - Phi3-mini - StableLM-2-zephyr-1.6B - Qwen1.5-1.8B - Hermes2-Pro-Llama-3-8B to prebuilt models - Updates on `ModelRecord` fields - For detail see: mlc-ai#435 - Update all WASMs - For detail see: mlc-ai#433 - Update all WASMs to v0.2.39 - Support grammar for Llama3, hence update examples/json-mode to use `Llama3` and `Hermes2-pro-Llama3-8B` for function calling in `examples/json-schema` - Use `loglevel` package: - For details see mlc-ai#427 - Fix `index.js.map` issue for Vite - mlc-ai#420 - Enhance error handling and ServiceWorker ### TVMjs TVMjs compiled at apache/tvm@71f7af7 - Main changes include: - apache/tvm#17031 - apache/tvm#17028 - apache/tvm#17021 ### WASM version - All wasms updated to 0.2.39 via mlc-ai/binary-mlc-llm-libs#123 for new MLC-LLM runtime (mainly grammar)
jingyi-zhao-01
pushed a commit
to jingyi-zhao-01/web-llm
that referenced
this pull request
Dec 8, 2024
) Follow up from mlc-ai#427 to prevent the following type issue introduced on `v0.2.39`: <img width="1328" alt="image" src="https://github.com/mlc-ai/web-llm/assets/418083/3b2d028f-71af-4e77-a779-e4176225b92a"> This issue fails type-checking [[reference](https://github.com/felladrin/MiniSearch/actions/runs/9298738476/job/25591213310?pr=356)] and forces users to define the `logLevel` config. But in fact, `logLevel` already has a default value and was intended to be an optional parameter. This PR fixes it.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR introduces a new package,
logLevel, which is a lightweight logging javascript library for managing logging levels and filtering debug logs in production.https://github.com/pimterry/loglevel
We exposed
logLevelas part of the engine config to allow users to modify it. The default log level isWARN.In
TRACElevel:In
WARNlevel: