Skip to content

create rollup typings for messaging #4974

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

Merged
merged 3 commits into from
Jun 4, 2021
Merged

create rollup typings for messaging #4974

merged 3 commits into from
Jun 4, 2021

Conversation

Feiyang1
Copy link
Member

@Feiyang1 Feiyang1 commented Jun 3, 2021

We need rollup typings to generate overloads for interop in messaging-compat.

@changeset-bot
Copy link

changeset-bot bot commented Jun 3, 2021

⚠️ No Changeset found

Latest commit: 2fd5781

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@google-oss-bot
Copy link
Contributor

google-oss-bot commented Jun 3, 2021

Binary Size Report

Affected SDKs

  • @firebase/firestore

    Type Base (61fd238) Head (6bef7ae) Diff
    browser 284 kB 284 kB -2 B (-0.0%)
    module 284 kB 284 kB -2 B (-0.0%)

Test Logs

@google-oss-bot
Copy link
Contributor

google-oss-bot commented Jun 3, 2021

Size Analysis Report

Affected Products

No changes between base commit (61fd238) and head commit (6bef7ae).

"api-report": "api-extractor run --local --verbose",
"type-check": "tsc --noEmit"
"api-report": "yarn api-report:rollup && yarn api-report:api-json",
"api-report:rollup": "TS_NODE_COMPILER_OPTIONS='{\"module\":\"commonjs\"}' ts-node ../../repo-scripts/prune-dts/extract-public-api.ts --package messaging-exp --packageRoot . --typescriptDts ./dist/index.d.ts --rollupDts ./dist/private.d.ts --untrimmedRollupDts ./dist/internal.d.ts --publicDts ./dist/index-public.d.ts",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just out of curiosity, when do we use ts-node and ts-node-script?

Copy link
Member Author

@Feiyang1 Feiyang1 Jun 4, 2021

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ts-node-script reads the tsconfig from the source directory where the script lives, while ts-node loads tsconfig from the cwd. This behavior has changed in v10 where ts-node behaves the same way as ts-node-script by default. (we haven't updated to v10 yet)

In most cases, you'd want to use ts-node-script because you want to use the tsconfig of the script.

Here, we should really use ts-node-script, but it won't matter once we upgrade to v10, so I will keep it as is for now.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Well, ended up updating to ts-node-script

@Feiyang1 Feiyang1 merged commit f41d11b into master Jun 4, 2021
@Feiyang1 Feiyang1 deleted the fei-fcm-build branch June 4, 2021 22:46
@firebase firebase locked and limited conversation to collaborators Jul 5, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants