-
-
Notifications
You must be signed in to change notification settings - Fork 80
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
chore(deps): upgrade all dependencies and ember-cli #135
Conversation
Sweet. Now this build also fails. So it's not just me. Haha. 😄 |
I've tested my branch with a yarn resolution in our application using the latest ember-cli and it works perfectly now! 🚀 |
Resolved merge conflicts by rebasing onto latest master. |
@nlfurniss @xg-wang Any chance that we can merge this? Happy to rebase again. |
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.
Yeah would be great to get this in.
This will be a breaking change as it drops node 6 and ember-cli < 2.12
We can get this in after a patch version #140 then do a major bump.
I've rebased onto the latest master. 😊 |
I think we can make it a new major after #143, which will be a new minor. |
package.json
Outdated
"loader.js": "^4.2.3", | ||
"mocha": "^5.2.0" | ||
}, | ||
"engines": { | ||
"node": "6.* || 8.* || >= 10" | ||
"node": "8.* || >= 10" |
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.
@buschtoens why did you drop Node 6 support?
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.
To quote Jeff Sessions: "I do not recall."
I think it was because one of the dependencies I've updated dropped Node 6 support. I can checkout the PR again later and see, whether this is actually the case and whether we can avoid that one dep to get this out the door.
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.
I've rebased and reverted that commit. Let's see, if the Travis goes green. :)
https://travis-ci.org/ember-cli/ember-fetch/builds/455055560
This reverts commit 077f3fd.
|
||
it(`${ | ||
preferNative ? 'Prefers' : "Doesn't prefer" | ||
} native fetch as specified`, async function() { | ||
await output.build(); | ||
} native fetch as specified`, co.wrap(function*() { |
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.
Why use co instead of async?
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.
Because co is supported by Node 6 and async is not
I'm having trouble getting
ember-fetch
to run with the latestember-cli
. Prior to this PRbroccoli-rollup
would not find theenv
preset.Now I'm getting a different error:
Anyhow, this PR might be beneficial either way.