Flex-layout: Beta 11 is not reachable

[bogacg]

I've changed my package.json for beta 11 but getting this error:

npm ERR! code ETARGET
npm ERR! notarget No matching version found for @angular/[email protected]

[arlowhite]

I see this version in npm: '2.0.0-beta.10-4905443': '2017-11-05T15:18:57.776Z'

Was there an issue with the npm release?

[snarum]

I'm having trouble with angular 5.0.0 and flex, and hoping beta-11 will solve this.

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

[nikonthethird]

@snarum what you're seeing is #479, there's more information there.

In the meantime, as long as beta 11 is not available on NPM, something that worked for me is to use the Github builds instead of NPM, by changing your package.json:

"@angular/flex-layout": "git+https://github.com/angular/flex-layout-builds.git"

npm install still complains that @angular/[email protected] requires a peer of @angular/core@~4.4.4 but none is installed. but everything works so far.

[arlowhite]

If the newest flex-layout depends on Angular5, I think it would be good to follow the material2 example and bump the version to 5.0.0-*. But if it's backwards compatible I suppose it should stay at 2.0.0-*

[bogacg]

In my app I see Flex-Layout bugs like layout not being rendered consistently across all browsers supposedly it supports but I don't see any version related error messages for Angular 5. Also some bugs like window resize renders one way correctly but not other, team is aware of that. If there are patches need to be applied for different browsers by developers, they need to be clearly put into documents. If these are to be fixed by the team, they should. A project under Angular umbrella and not seeing any move forward is troubling.

[adeptues]

this project is dead

[jocor87]

I am getting the error:

npm WARN @angular/[email protected] requires a peer of @angular/common@~4.4.4 but none is installed. You must install peer dependencies yourself.

[kylecordes]

I'm thinking there must be some bigger problem than just "made a release and forget to npm publish". When the team is back in action (there's just people, and people have things come up to distract from projects!) I'm hoping to find out it's a not-too-big problem.

[ardatan]

So any life sign?

[majodi]

I'm following the install instructions and see that @angular/core@~4.4.4 is required. What are the implications if I just go ahead and ignore the warning? Or should I wait for an update of this package?

[captantan]

I have been using this with the newest angular versions without issues beyond the warnings from npm.

[ThomasBurleson]

@bogacg - We plan on releasing Beta.12 today with:

• fixes to npm releases
• dep changes to Angular ~5.1.0 and RxJS 5.5.x (in alignment with @angular/material)

[ThomasBurleson]

Fixed with today's 2.0.0-beta.12 release. See SHA 62457a5972 and CHANGELOG

[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._}