@fabien0102/angularfire2
Advanced tools
Changelog
2.0.0-beta.6-preview (2016-11-02)
A TypeScript issue with the previous release has been fixed, where errors about a missing firebase
namespace were reported. For
applications that worked around this issue by manually adding the firebase.d.ts
typings to tsconfig.json
, those typings
should now be removed since the firebase namespace should automatically be resolved within AngularFire.
See this issue for more context.
<a name="2.0.0-beta.5"></a>
Changelog
2.0.0-beta.5 (2016-09-15)
The way this project is packaged has changed to be consistent with other Angular packages. Previously:
angularfire2.js
as the main entry point.es6
directory which contained es2015 modules and es2015 JSmain
and jsnext:main
fields, pointing to angularfire2.js
and es6/angularfire2.js
, respectively.Now:
bundles/angulafire2.umd.js
main
field of package.json
points to bundles/angularfire2.umd.js
.jsnext:main
, we're using the module
field of package.json to point to index.js
.angularfire2.js
being the main entry point, an index.js
has been added (though angulafire2.js hasn't changed significantly).If you're using Rollup or Webpack, they should just work with this new setup (please open issues if not). If using SystemJS, you should be able to
add format: 'esm'
inside of the packages configuration, and it should load and parse the es2015 modules correctly.
The addition of the umd bundle will also make it possible to use AngularFire2 in a <script>
tag, such as in a plunker or JSBin. The library is
exported on a global called angularFire2
.
<a name="2.0.0-beta.4"></a>