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
I believe this issue will require an npm package release.
Possible Solution:
I know develop does not use always-tail2. I think a smaller than tail-stream change in develop might be switching from always-tail2 to a newer version of node-tail (just tail) with correct options.
The text was updated successfully, but these errors were encountered:
Duplicate issue of #6
Root cause: Debug security issue: debug-js/debug#501
Always-tail2 issue: azilber/always-tail2#2 has the following issue open
Worth noting that recent additions to node-tail might make always-tail2 obsolete.
https://github.com/lucagrulla/node-tail has newer releases since then.
lucagrulla/node-tail#104 fixed in version 2.0.4.
Ran across this when trying to clean up npm audit issues in https://github.com/viktorgullmark/exilence-next . I will be making an issue there waiting on this change.
I believe this issue will require an npm package release.
Possible Solution:
I know develop does not use always-tail2. I think a smaller than tail-stream change in develop might be switching from always-tail2 to a newer version of node-tail (just tail) with correct options.
The text was updated successfully, but these errors were encountered: