Closed knownasilya closed 5 years ago
@knownasilya Thanks! I'll do a review asap. Is there a particular reason why you switched from yarn
to npm
?
For npm audit, since yarn doesn't do that. I can do yarn if you want.
Oh, didn't know that. Npm does it automatically on install.
Thanks @dfreeman for the hint. @knownasilya I think we should go with yarn.
@fsmanuel done
@knownasilya can you also run the blueprints again. All the npm run
commands should be replaced by yarn
. I'm not 100% sure but if I recall correctly the blueprint should detect yarn and act according to it.
@fsmanuel for the travis config?
@fsmanuel looks like both 2.12 and 2.16 fail.
@knownasilya not sure how to make ember-data
work for the release channels but I asked here: https://github.com/ember-cli/ember-source-channel-url/issues/5#issuecomment-454144428
Ping @fsmanuel
@knownasilya seems like we need jquery
for lts-2.16
and lts-2.12
needs ember-cli-shims
.
Here is how we can setup the right ember-data
versions for the release channels: https://github.com/ember-cli/ember-source-channel-url/issues/5#issuecomment-454312491
@knownasilya do you need more help or suggestions?
Just haven't had time to dig back into this. I'll try to look at it this week.
@knownasilya No rush!
Hey @knownasilya, thanks for all the work! I took over your branch here #311 and fixed the nasty ember try config. I'll ping you as soon as I release a new version.
Nice, great work!
Ran ember-cli-update and then the codemods. Fixed the test helpers and linting. The dummy app might need some styling fixes after the linting. Will have a look later.
Not sure if this requires a major version bump since the support matrix might have changed a bit.