angularfire2 2.0.0-beta.5 isn't visible on npmjs

[asadsahi]

It is self evident if you try to install this version or search on npmjs.com.

[jwuliger]

Yes please release it. We need it badly for our project. Thanks!!

[davideast]

@asadsahi @jwuliger There's an issue with AoT compilation that we are looking into. Rest assured we are working on it :)

[jwuliger]

@davideast Thanks David!

[asadsahi]

@davideast should angularfire 2 be worried about AoT right now when tooling like cli / official documentation doesn't give any clue to what AoT is? To most of us this is just a concept in the air right now.

[ivoviz]

@asadsahi Getting AoT working is not really a big deal even on a CLI made project, and I'm actually waiting for angularfire2 to work with AoT. Also the latest release isn't really a deal breaker, one could just use rxjs beta.10 until it's released, but AoT is something that should definitely work now that Angular 2.0.0 is released and I'm really glad they're working on it!

[asadsahi]

@ivoviz AoT definitely sounds good, its just frustration caused by last release of angularfire2 could be avoided by a subsequent release targeting AoT. Not sure if the priority was to fix critical issues than AoT.

[ivoviz]

@asadsahi Imo they just forgot to release initially and later on found an issue with AoT. Probably they'll fix it soon and then do a release. I understand your frustration, but the lib - with a small modification - still works, so I wouldn't really sweat it. Let's hope they'll do a release soon with AoT fixes though!

[davideast]

@asadsahi @ivoviz It's important that we try not to knowingly release bugs into production. Outside of the AoT issue we have some more testing to do as there were a fair amount of changes to our test setup from the RC7 upgrade.

We plan on cutting a next release soon, we'll let you know when it's out.

[jeffbcross]

Hey folks, I've published a pre-release version of the package behind a tag. It includes some packaging changes introduced in #510 which haven't yet been merged into master. You can get it by npm install angularfire2@next.

I'd appreciate any feedback if there are issues with the new packaging.

[jeffbcross]

Sorry for the inconvenience, I pushed the beta.5 tag to Github as I was preparing to do the release, and then ran into some build issues. As I was correcting the build issue, I wanted to take care of a couple of things to make AngularFire2 AoT-compile-friendly.

[ivoviz]

@jeffbcross Thanks! I've just tried it, it's still not working for AoT, but at least it's a new error now. Previously I had Could not resolve 'angularfire2' from .../src/app/app.module.js, now it's Could not resolve '_stream_writable' from .../node_modules/angularfire2/node_modules/firebase/database-node.js

[jeffbcross]

Thanks, will look into it. We should add an AoT integration test (though
not necessarily block this release on it).
On Thu, Sep 15, 2016 at 5:51 PM John Smith notifications@github.com wrote:

@jeffbcross https://github.com/jeffbcross Thanks! I've just tried it,
it's still not working for AoT, but at least it's a new error now.
Previously I had Could not resolve 'angularfire2' from
.../src/app/app.module.js, now it's Could not resolve '_stream_writable'
from .../node_modules/angularfire2/node_modules/firebase/database-node.js

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#511 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAcTV2q5jLE1EE5NEepMiQgGNMSJl_hQks5qqef0gaJpZM4J-QeS
.

[ivoviz]

Just to be sure I'm doing it right, my rollup config is something like this:

export default {
  entry: 'src/main.js',
  dest: 'dist/build.js',
  sourceMap: false,
  format: 'iife',
  plugins: [
      nodeResolve({jsnext: true, module: true}),
      commonjs({
        include: ['node_modules/rxjs/**', 'node_modules/angularfire2/**'],
      }),
      uglify()
  ]
}

[asadsahi]

@jeffbcross latest preview package has fixed #496 at least 👍

Here are my packages:

   "angularfire2": "^2.0.0-beta.5-preview",
    "firebase": "3.4.0",
    "rxjs": "^5.0.0-beta.12",
    "zone.js": "^0.6.23"

[ivoviz]

@jeffbcross It's just a wild guess, but it seems like it's trying to load the node version of firebase (firebase-node) instead of the browser one (firebase-browser).