Flex-layout: Angular v5

[xban1x]

Bug, feature request, or proposal:

Bug

What is the expected behavior?

Work out of the box.

What is the current behavior?

Does not.

What are the steps to reproduce?

http://prntscr.com/h56trt

What is the use-case or motivation for changing an existing behavior?

Using the latest Angular version with FlexLayout.

Which versions of Angular, Material, OS, TypeScript, browsers are affected?

http://prntscr.com/h56uej

Is there anything else we should know?

Just replace OpaqueToken with InjectionToken.

[yuraantonov11]

the same problem

[kferstl]

for me it helped to install the latest flex-layout version by specifying the version explicitly:

npm install --save @angular/[email protected]

the problem behind that was:
@angular/[email protected]. was renamed back to @angular/[email protected], updating npm packages often uses that version. Specify the latest beta manually to use it.
see: https://github.com/angular/flex-layout/blob/master/CHANGELOG.md#200-beta7-2017-03-17

[xban1x]

@kferstl will try it out. But looking at current master you are correct. It is a NPM issue.

[kevindqc]

if I update to beta.10 (had rc.1 before), I get this:

npm WARN @angular/[email protected] requires a peer of @angular/[email protected] but none was installed.
npm WARN @angular/[email protected] requires a peer of @angular/[email protected] but none was installed.

[zhentian-wan]

OpqueToekn was removed form Angular5

[ThomasBurleson]

Beta.10 has been recently released.

• We are fixing current peerDependency issues.
• We are aware of the npm update issue.
-

Both are known, registered issues.

[angular-automatic-lock-bot[bot]]

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{_This action has been performed automatically by a bot._}