Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

chore: write es6 modules to esm directory #310

Closed
jeffbcross opened this issue Jun 30, 2016 · 0 comments
Closed

chore: write es6 modules to esm directory #310

jeffbcross opened this issue Jun 30, 2016 · 0 comments

Comments

@jeffbcross
Copy link
Contributor

Should publish them to both es6 and esm for one release, remove es6 on the following release.

@jeffbcross jeffbcross added this to the Beta.3 milestone Jun 30, 2016
@jeffbcross jeffbcross self-assigned this Jun 30, 2016
jeffbcross added a commit to jeffbcross/angularfire2 that referenced this issue Jun 30, 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.

Fixes angular#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.

Fixes angular#310
# for free to join this conversation on GitHub. Already have an account? # to comment
Projects
None yet
Development

No branches or pull requests

1 participant