Updating Ember to v3.0.0

[Alonski]

This is a Work In Progress

I have currently updated Ember to v2.18.2

While trying to update to v3.0.0 I ran into an issue with this deprecation:
An addon is trying to access project.nodeModulesPath. This is not a reliable way to discover npm modules. Instead, consider doing: require("resolve").sync(something, { basedir: project.root }). Accessed from:

I have updated all plugins that I could with all tests passing (might have missed a few)
Currently there are still some addons that are not updated enough.
I will try to create PRs for these addons to fix them and would love some help.
These are:

1. https://github.com/mike-north/ember-anchor - Fixed by using forks. Not a long term solution
2. https://github.com/kimroen/ember-cli-document-title - PR accepted. New version updated.
3. https://github.com/cardstack/ember-data-fastboot - PR accepted. New version updated. Thanks @ef4
4. https://github.com/HeroicEric/ember-normalize - This addon is deprecated. Removed. Add deprecation notice to README HeroicEric/ember-normalize#19

Update 3/19/18

I have successfully updated to v3.0.0 and the app runs however tests are failing. Working on getting them fixed

Update 4/9/18

I reupdated to v3.0.0 but without the new test syntax. I couldn't get that running

[Gaurav0]

@Alonski That is an ember-cli deprecation. It did not prevent my work app from upgrading to Ember 3.0.

[Alonski]

@Gaurav0 I am trying to update Ember-CLI to v3.0.0 along with all Ember dependencies.

From my testing this deprecation is causing build errors in v3.0.0

[sivakumar-kailasam]

In case you've opened a PR for this, can you make an issue in this repo linking to that PR so that we can swap it back when it gets merged?

[sivakumar-kailasam]

Note for reviewers: There's a bourbon update in this PR, we'll have to look around the app to make sure styles are intact before we merge

[toddjordan]

to address #469

[Alonski]

Thanks @toddjordan. I forgot to link to the issue

[sivakumar-kailasam]

I'm merging this PR into the 3-0-upgrade branch on this repo so that we can iterate over this and then merge to master. Thanks once again for tackling this @Alonski 🎉

[Alonski]

@sivakumar-kailasam awesome. If I have fixes for a few things should I make a PR to that branch?

[sivakumar-kailasam]

@Alonski yes please :)