Closed cjpillsbury closed 6 months ago
@cjpillsbury is attempting to deploy a commit to the Mux Team on Vercel.
A member of the Team first needs to authorize it.
All modified and coverable lines are covered by tests :white_check_mark:
Project coverage is 72.33%. Comparing base (
3ea80df
) to head (f1d5603
). Report is 39 commits behind head on main.
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
The latest updates on your projects. Learn more about Vercel for Git ↗︎
Name | Status | Preview | Comments | Updated (UTC) |
---|---|---|---|---|
media-chrome | ✅ Ready (Inspect) | Visit Preview | 💬 Add feedback | Mar 19, 2024 11:39pm |
media-chrome-demo-nextjs | ✅ Ready (Inspect) | Visit Preview | 💬 Add feedback | Mar 19, 2024 11:39pm |
media-chrome-docs | ✅ Ready (Inspect) | Visit Preview | 💬 Add feedback | Mar 19, 2024 11:39pm |
NOTE: Per a conversation with @heff and prompted by @mmcc's gut example/pseudo-code on importing, at least at this stage, we decided to call an audible and not create multiple npm packages / restructure our codebase to a monorepo. As this was decided between just the two of us, we can certainly discuss more. Additionally, we can merge this as is but hold off on any "official support" and corresponding comms/documentation unless/until we have sufficient consensus on single package vs. multi-package for the new react-specific code, especially since this should have no impact on prior use cases of Media Chrome.
Demo usage/smoke testing: https://media-chrome-demo-nextjs-git-fork-cjpillsbury-experi-b8bc5e-mux.vercel.app/