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
A transitive dependency called isbinaryfile is used by scandal, our library for doing project-wide token searching. It uses [email protected]. That version’s package.json defines a main of ./lib/index.js — a path that does not exist in the package! — so Node complains; but the package still loads properly because there's an index.js at its root, so the default handling logic kicks in. So it complains loudly but ends up doing the right thing.
This never got fixed in the 2.X.X releases, so fixing this would involve upgrading to isbinaryfile@^3. That's certainly doable, but involves an API change. That means we'd have to change scandal itself, and we'd probably want to convert it to JavaScript if we touched it. So it's not likely to get fixed in the short term.
A quick (but hacky) fix would be to filter out any log lines that mention it in src/task.js. I'd do this as a stopgap if it were truly a problem, but I doubt it's worth it.
I'm surprised I've never gotten this log spam. (Maybe I've just never noticed it?)
Thanks in advance for your bug report!
What happened?
It only spammed my console sometimes, I do not know how to trigger it.
Pulsar version
1.124.2025022507-next
Which OS does this happen on?
🪟 Windows
OS details
10
Which CPU architecture are you running this on?
x86_64/AMD64
What steps are needed to reproduce this?
Don't know.
Additional Information:
No response
The text was updated successfully, but these errors were encountered: