feat: Angular 5.0 compatibility

[ryzy]

Makes it compatible with Angular 5. Tested, works in ng5 app and will continue to work on ng4.

OpaqueToken was deprecated with v4 and has been completely removed in v5.

If you ok with it, I'll send a sync of ./dist dir.

Thanks, cheers!

[ryzy]

Also, if you willing to switch to angular-cli for dev, I could update whole project to use Angular 5 (i.e. the example app).

[ryzy]

Hey @PillowPillow,

I see there's already another PR there with the same. I get you must be busy, but, this one is easy to merge (two lines change + dist) and we're on Angular 5.

[ryzy]

PS. If you're looking for help with maintaining this one, happy to help - working full time with Angular, using your package in my company, we like it, so can help at least with minimal maintenance and responding to PRs.

[aurimukas]

Agree with @ryzy we should know, if this module is not maintained any more.. we should get someone who checks it more often or do a fork..

[svitlychnyi]

+1

[civicwar]

@ryzy
careful with those false positive changes like:

• Indentation ( TAB , SPACE )
• CRLF / LF
• EOF

because i see many changed files with false positives.

[RasmusTG]

+1

[nblavoie]

@PillowPillow We need this ASAP. Thanks.

[Gillardo]

@PillowPillow ?? Can you merge please?

[mbenzenhoefer]

+1

[tommueller]

+1

[stas-kh]

+1

[nblavoie]

Can we simply fork the project with the included fixes?

[svitlychnyi]

Author is, most probably, just has no time at the moment, but he is active:
Contribution activity: November 7, 2017 (32 contributions in private repositories)

Lets just wait for some time.

[Gillardo]

I am just using branch by @ryzy . works perfectly!

[svitlychnyi]

Aha, I told you :)

[Gillardo]

can you tell us when this will be updated on npm please?

[nblavoie]

@Gillardo +1 !

[atigm]

While waiting for tag, you can use the master code :
npm install git://github.com/PillowPillow/ng2-webstorage --save
It's working for me

[PillowPillow]

During the night, it will comes with some bug fixes.

[ryzy]

@PillowPillow thanks for merging and a new release, great job!

BTW @civicwar agree, the only reason why there were changes in this is because the repo contains also compiled dist version of the package and it's the result of whatever ngc compiler produces. My change was in one line only :D @PillowPillow might decide at some point to change it (e.g. prepare the dist just for npm publish and exclude it from the source code of the repository).

[PillowPillow]

I'm keeping the dist in the repo for those who prefers use bower.
Since i'm not maintaining a bower repo, they can take the sources from github.