-
Notifications
You must be signed in to change notification settings - Fork 182
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
Please upgrade to winston 3.x to avoid licensing issue #195
Comments
Its been 2+ years... Can we move or get a response on this? |
Ahh I see the upgrade path is a nightmare in the unit testing. |
Bumping wiston with |
Yea, I'm maintaining this repo, but I think I'll tell the other owners that we might want to archive this repo. I don't feel like updating its core, instead I think there are alternatives, something simple like https://github.com/heapwolf/prompt-sync for example as suggested by another user, I also made http://github.com/caub/prompt-ajv for an almost drop-in replacement |
- diff (via vows): GHSA-h6ch-v84p-w6p9 - async (via winston): GHSA-fwr7-v2mv-hh25 Related db-migrate/node-db-migrate#779 Related 4736c82 Closes flatiron#195
Note the comment from #226 (comment) but if you're on prompt 1.3.0 you can do an update and get winston 2.4.6 (I ran |
Winston 2.x had a dependency on the
cycle
npm package which has a problematic licensing situation that they refuse to fix. This was subsequently fixed in 3.0.0-rc0.Would be nice if
prompt
can upgrade to Winston 3.x to avoid this issue.The text was updated successfully, but these errors were encountered: