Skip to content
Discussion options

You must be logged in to vote

Hey @glaypan 👋 Thanks for the detailed report — I'll look into it and ship a fix soon so the install doesn't depend on that version window.

Quick context on the error: @huggingface/tasks isn't a direct wigolo dependency — it gets pulled in transitively by the ML reranker (@huggingface/transformers). The ^0.21.28 range is real (not a typo), but you caught it during a gap where the transformers chain requested a version that hadn't finished propagating to npm yet, so your resolver couldn't match it.

For the time being, could you try clearing your npm cache and reinstalling? That version is on the registry now, so a fresh resolve should pick it up:

npm cache clean --force
npx -y wigolo@lates…

Replies: 1 comment

Comment options

You must be logged in to vote
0 replies
Answer selected by KnockOutEZ
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants