-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Command never outputs anything #50
Comments
I recommend not using |
@sazzer , are you running with modules ( It looks like My co-workers and I are seeing the same issue you describe, and we're using modules. |
Again: we have not published this module to npm. We cannot guarantee what code is being pulled from npmjs.com. |
We finally gained publishing rights to the package on npm. I have published v2, but nothing in it has changed except for dependency updates. A PR to solve this issue would be welcomed. |
I've been playing with this because it seems incredibly useful, and it doesn't work. It never outputs anything :(
It seems that the problem is down to
require.main === module
inindex.js
. This always returnsfalse
for me, no matter what.This is on Node v18.7.0, and I've been running the tool with both
npx pino-filter
andnode ./node_modules/.bin/pino-filter
. If I change that conditional to always be true then it works great, but for some reason with it as-is it doesn't work :(Cheers
The text was updated successfully, but these errors were encountered: