flex-layout: 2.0.0-beta.11 is not published
Bug, feature request, or proposal:
Bug/request – according to the releases, the latest artifact is 2.0.0-beta.11
but the NPM indicates beta.10
is latest available (i.e., there’s no 2.0.0-beta.11
).
What is the expected behavior?
I get the error below when I try to use @angular/flex-layout@2.0.0-beta.11
:
npm ERR! notarget No compatible version found: @angular/flex-layout@2.0.0-beta.11
npm ERR! notarget Valid install targets:
npm ERR! notarget 2.0.0-rc.1, 2.0.0-beta.10-4905443, 2.0.0-beta.10, 2.0.0-beta.9, 2.0.0-beta.8, 2.0.0-beta.7, 2.0.0-beta.5, 2.0.0-beta.4, 2.0.0-beta.3, 2.0.0-beta.1, 2.0.0-beta.0
Which versions of Angular, Material, OS, TypeScript, browsers are affected?
Angular 5, Material 5, Linux, TypeScript 2.4.2
About this issue
- Original URL
- State: closed
- Created 7 years ago
- Reactions: 9
- Comments: 15
Hi @krag-123 – this doesn’t appear to be a duplicate of #344 but it’s related. This issue is about either
beta.11
not being published, or the release notes being wrong by mentioningbeta.11
instead ofrc.1
. Since #344 indicates thatrc.1
is actuallybeta.6
, it appearsbeta.11
not being published is the problem. I have focused this issues title and description accordingly. So, untilbeta.11
is published your best bet is likelybeta.10
for Angular 5 support.I believe rc.1 was released around the time of beta.9 but got renamed to beta.9
rc.1 is not the latest version, it is actually an old version.
i think duplicate with #344
Duplicate of #489
I’ve tried to use
"@angular/flex-layout": "2.0.0-beta.11"
and there’s nonpm package
with that version, there’s2.0.0-beta.10-4905443
which I think it’sbeta.11
with a wrong version published.@gzamb – I’m now using
@angular/flex-layout@2.0.0-rc.1
in my Angular 5, Angular Material 5, and Angular CLI 1.5 based application; there are no related warnings.