- Notifications
You must be signed in to change notification settings - Fork951
build: new internal builds for google3#9139
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
base:main
Are you sure you want to change the base?
Uh oh!
There was an error while loading.Please reload this page.
Conversation
changeset-botbot commentedJul 2, 2025 • edited
Loading Uh oh!
There was an error while loading.Please reload this page.
edited
Uh oh!
There was an error while loading.Please reload this page.
|
google-oss-bot commentedJul 2, 2025 • edited
Loading Uh oh!
There was an error while loading.Please reload this page.
edited
Uh oh!
There was an error while loading.Please reload this page.
Size Report1Affected Products
Test Logs |
google-oss-bot commentedJul 2, 2025 • edited
Loading Uh oh!
There was an error while loading.Please reload this page.
edited
Uh oh!
There was an error while loading.Please reload this page.
Size Analysis Report1This report is too large (864,920 characters) to be displayed here in a GitHub comment. Please use the below link to see the full report on Google Cloud Storage.Test Logs |
Create new builds that are only triggered during the internal google3 build, for google3 consumers:
It also doesn't look like we need to do the convoluted rollup config swap that we do in the google3 import script (internal link:https://source.corp.google.com/piper///depot/google3/third_party/javascript/firebase/updateThirdParty.sh;rcl=666835113;l=91) when we have a special build:internal script that can simply call the other config, so I changed that.
I assume we need to roll up new typings for each of the new bundles, so I added a step to generate those.
An unfortunate complication is that simply exporting
*
from each package leads to name collisions so every module needs to be namespaced with the product name, so thatinitializeApp
must be referred to asapp.initializeApp
for example. This is really going backwards toward the old compat packages but the g3 ecosystem doesn't really give us much choice.Also I noticed the rollup-internal.config.js builds every file that the main one does, including the non-cdn ones (such as the individual product entry points under firebase/) which doesn't seem necessary as they're not included in any BUILD target in google3, so I removed those. Will see if this causes a problem.
I will leave this as a branch and a draft that can be imported into google3 and iterated on based on whether it works there.