Skip to content
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

Closed
wants to merge 1 commit into from

Conversation

root-io
Copy link
Contributor

@root-io root-io commented Mar 18, 2019

No description provided.

@root-io
Copy link
Contributor Author

root-io commented Mar 18, 2019

CHANGELOG.md Outdated Show resolved Hide resolved
CHANGELOG.md Show resolved Hide resolved
package.json Outdated Show resolved Hide resolved
@root-io root-io force-pushed the feature/warn-new-update branch 3 times, most recently from a74e04e to c6f634f Compare March 22, 2019 16:45
@root-io root-io assigned arnaudbesnier and unassigned root-io Mar 22, 2019
Copy link
Member

@arnaudbesnier arnaudbesnier left a 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.

@root-io
Copy link
Contributor Author

root-io commented Mar 29, 2019

I think that's because the packages versions are set with ^

@arnaudbesnier arnaudbesnier changed the base branch from master to devel April 4, 2019 07:09
@arnaudbesnier arnaudbesnier requested a review from SeyZ April 4, 2019 07:29
@SeyZ SeyZ force-pushed the feature/warn-new-update branch 2 times, most recently from 8cb6e25 to 90ba453 Compare April 4, 2019 07:33
@SeyZ
Copy link
Member

SeyZ commented Apr 4, 2019

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.

@SeyZ SeyZ closed this Apr 4, 2019
@SeyZ SeyZ deleted the feature/warn-new-update branch May 2, 2019 12:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants