refactor: replace default exports with named exports

[dtychshenko]

All default exports have been replaced with named exports across core packages, plugins, and React components. External dependencies have been verified to be not using the affected default exports that changed. Closes #669.

Change Type (required)

Indicate the type of change your pull request is:

• patch
• minor
• major
• N/A

Does your PR have any documentation updates?

• Updated docs
• No Update needed
• Unable to update docs

Release Notes

All default exports have been replaced with named exports across core packages, plugins, and React components.

Affected packages:

• @player-ui/make-flow: identify function
• @player-ui/partial-match-registry: createObjectMatcher function
• @player-ui/player: Logger classes and view plugins
• @player-ui/react: ReactPlayer component and OnUpdatePlugin
• @player-ui/metrics-plugin: MetricsCorePlugin class
• @player-ui/auto-scroll-manager-plugin-react: scrollIntoViewWithOffset

[KetanReddy]

@sugarmanz any reason these changes could cause a timeout on the android emulation stage?

[dtychshenko]

@sugarmanz any reason these changes could cause a timeout on the android emulation stage?

I suspect it may have something to do with the android-test-fork job itself. I noticed that all the PRs that are being built and merged successfully are running from the main repo branches that execute android-test-trunk, while I don't have access to the main repo and using a forked repo.

[KetanReddy]

@sugarmanz any reason these changes could cause a timeout on the android emulation stage?

I suspect it may have something to do with the android-test-fork job itself. I noticed that all the PRs that are being built and merged successfully are running from the main repo branches that execute android-test-trunk, while I don't have access to the main repo and using a forked repo.

Ah, that could be it. Forked jobs don't have access to our build cache so there might be some issue with testing if the the test is already cached where it is failing instead of returning false. Let me pull this branch into the repo and run it through CI from there.

[sugarmanz]

@sugarmanz any reason these changes could cause a timeout on the android emulation stage?

It did time out due to no output, but that doesn't mean it wasn't building things behind the scenes. I guess I shouldn't have muted all the logs — was just trying to make it apparent that we were checking for cached results vs actually building/testing. I'll open up a PR to let Bazel log normally during the cache-check.

[KetanReddy]

@sugarmanz any reason these changes could cause a timeout on the android emulation stage?

It did time out due to no output, but that doesn't mean it wasn't building things behind the scenes. I guess I shouldn't have muted all the logs — was just trying to make it apparent that we were checking for cached results vs actually building/testing. I'll open up a PR to let Bazel log normally during the cache-check.

Ah, I know circle will kill a job if it has no log output for 10m so if it was doing something it probably didn't show as such so it got killed.

[KetanReddy]

I think the biggest question here @player-ui/reviewers is if this is going to be a major release? If so we probably need to stage this while we burn down the pre first major list.

[spentacular]

Thanks for finding these and cleaning them up! LGTM.