-
Notifications
You must be signed in to change notification settings - Fork 106
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
[+] Technical - Warn users if an update of Lumber is available #199
Conversation
a74e04e
to
c6f634f
Compare
c6f634f
to
e46dd9d
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The package-lock.json does not seem to have the right package versions.
I think that's because the packages versions are set with |
e46dd9d
to
2de5e0b
Compare
8cb6e25
to
90ba453
Compare
90ba453
to
7c0b953
Compare
It's a great nice to have but honestly, I'm not a big fan to have a subprocess ran to check the version. It means when something goes wrong for any reason (process.exit(1)), the subprocess is still running. In addition, there're some issue related to the subprocess: yeoman/update-notifier#140. I prefer to close this PR at the moment. |
No description provided.