You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
BREAKING CHANGE:
Previously, es modules were published to the es6/ directory inside the npm
package. This change publishes them to the esm directory to be consistent
with other angular packages. Currently, the es6 directory is still published
in the npm package, but will be removed in a future release.
Fixesangular#310
jeffbcross
added a commit
to jeffbcross/angularfire2
that referenced
this issue
Jul 1, 2016
BREAKING CHANGE:
Previously, es modules were published to the es6/ directory inside the npm
package. This change publishes them to the esm directory to be consistent
with other angular packages. Currently, the es6 directory is still published
in the npm package, but will be removed in a future release.
Fixesangular#310
Should publish them to both es6 and esm for one release, remove es6 on the following release.
The text was updated successfully, but these errors were encountered: