feat: add ui-chrome package with header/footer and helper components #827
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* pnpm upgrade for builder * add timeouts and retrys for builder errors * Filter Sentry extension errors from stack * handle corrupt JSON errors for CookieConsent
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
beeman
force-pushed
the
beeman/ui-chrome
branch
from
7d21f2e to
7a357c8
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Problem
The site header and footer live in
apps/weband are implemented using JavaScript and Bootstrap which means they can't be used in other apps that are using Tailwind 4Summary of Changes
Recreated the header and footer in the new
ui-chromepackage.Link/InlineLink/useRouter/usePathname) to@workspace/i18nDividercomponent using TailwindFixes #