-
Notifications
You must be signed in to change notification settings - Fork 926
Add installations CDN build and "firebase" entry point #6404
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
🦋 Changeset detectedLatest commit: 05cab10 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
Size Report 1Affected Products
Test Logs |
Size Analysis Report 1Affected ProductsNo changes between base commit (1d3a34d) and merge commit (3c00d7e).Test Logs |
This is great news! We're currently using CDN scripts for Flutterfire, and this is the last piece in the puzzle for us as you can read here. Do you have any idea on timeframe when this will be released? 😄 Thanks. |
We have a planned release this Thursday, if I am able to get it merged in time, it should go out then. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
These were not added in v9 because were under the impression that installations should not be a publicly exposed API but guide docs seem to indicate otherwise: https://firebase.google.com/docs/projects/manage-installations
This allows:
firebase/installations
andfirebase/compat/installations
- previously users could import@firebase/installations
and@firebase/installations-compat
directly, but they were not available on thefirebase
entry point (no@
)