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

Update ember-cli #91

Merged
merged 3 commits into from
Jul 16, 2018
Merged

Update ember-cli #91

merged 3 commits into from
Jul 16, 2018

Conversation

jacobq
Copy link
Contributor

@jacobq jacobq commented Jul 15, 2018

This PR is just optional clean-up. e.g. run ember-cli-update to sync-up with what ember-cli v3.2.0 generates for new addons, and also tweak CI setup.

package.json Outdated
},
"engines": {
"node": ">= 4"
"node": "6.* || 8.* || >= 10.*"
Copy link
Contributor Author

Choose a reason for hiding this comment

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

Oops, it looks like causes some problems. Do we want/need to keep support for node 4 to avoid a breaking change?

@jacobq jacobq force-pushed the update-ember-cli branch 3 times, most recently from a1c5af3 to 1fa0393 Compare July 15, 2018 19:56
appveyor.yml Outdated
@@ -7,15 +7,15 @@ init:
# Test against these versions of Node.js.
environment:
matrix:
- nodejs_version: "4"
Copy link
Owner

Choose a reason for hiding this comment

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

We can follow ember-cli here and remove version 4.

@jacobq
Copy link
Contributor Author

jacobq commented Jul 15, 2018

I just realized that e-cli 3.2.0 drops node 4.x support, so attempting to use it triggers an 'incompatible module' error. Hence, if we want to update here as I was thinking then we'd need to drop 4.x support. Perhaps that should wait until a major release. Feel free to close this PR if you don't want to drop node 4.x support.

@quaertym
Copy link
Owner

Please also rebase master and squash commits.

@jacobq
Copy link
Contributor Author

jacobq commented Jul 15, 2018

Do you want them all squashed (i.e. down to 1 single commit) or grouped (e.g. squash all of the e-cli updates, but keep the var->let/const separate)? (I was just following the recommendation of updating in stages but don't care either way.)

I've now rebased with master and squashed down to 3 commits (ember-cli update, var->let/const, and dependency upgrade).

@quaertym quaertym merged commit 8b6378a into quaertym:master Jul 16, 2018
@quaertym
Copy link
Owner

Thanks!

@Turbo87 Turbo87 mentioned this pull request Jan 2, 2019
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

2 participants