Skip to content

Check Node version early #5430 #5501

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

Closed
wants to merge 3 commits into from

Conversation

Pranav-Dakshina
Copy link

No description provided.

@facebook-github-bot
Copy link

Thank you for your pull request and welcome to our community. We require contributors to sign our Contributor License Agreement, and we don't seem to have you on file. In order for us to review and merge your code, please sign up at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need the corporate CLA signed.

If you have received this in error or have any questions, please contact us at [email protected]. Thanks!

@facebook-github-bot
Copy link

Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Facebook open source project. Thanks!

@stramel
Copy link

stramel commented Oct 21, 2018

Another PR #5482

I do like pulling from package but think we should use semver.satisfies to check the version

@Pranav-Dakshina
Copy link
Author

oh yeah, makes sense. but there are two node version checks both in index.js and createReactApp.js. Can't we remove the redundancy and add semver.satisfies in index.js @stramel

@stramel
Copy link

stramel commented Oct 21, 2018

IMO we remove the additional checks and only check in here using server instead of checking the parts of the version

@Pranav-Dakshina
Copy link
Author

cool. I will add the change in this PR.

@Pranav-Dakshina
Copy link
Author

#5430

@@ -11,3 +11,4 @@ npm-debug.log*
yarn-debug.log*
yarn-error.log*
/.changelog
yarn.lock
Copy link
Contributor

@ajwann ajwann Nov 15, 2018

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just curious, but why add yarn.lock to gitignore? Why not commit it?

@stale
Copy link

stale bot commented Dec 15, 2018

This pull request has been automatically marked as stale because it has not had any recent activity. It will be closed in 5 days if no further activity occurs.

@stale stale bot added the stale label Dec 15, 2018
@stale
Copy link

stale bot commented Dec 20, 2018

This pull request has been automatically closed because it has not had any recent activity. If you have a question or comment, please open a new issue. Thank you for your contribution!

@stale stale bot closed this Dec 20, 2018
@lock lock bot locked and limited conversation to collaborators Jan 8, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants