This repository has been archived by the owner on Feb 26, 2024. It is now read-only.
build(deps): update reach-ui monorepo to ^0.18.0 #927
Conversation
This file contains 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
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
![renovate-approve[bot]](https://avatars.githubusercontent.com/in/7394?s=60&v=4){kind=small}
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
renovate
bot
force-pushed
the
renovate/reach-ui-monorepo
branch
from
4ebf984
to
447a4e1
Compare
renovate
bot
force-pushed
the
renovate/reach-ui-monorepo
branch
from
447a4e1
to
ea08614
Compare
renovate
bot
force-pushed
the
renovate/reach-ui-monorepo
branch
from
ea08614
to
1f16fad
Compare
renovate
bot
force-pushed
the
renovate/reach-ui-monorepo
branch
from
1f16fad
to
679c0db
Compare
renovate
bot
force-pushed
the
renovate/reach-ui-monorepo
branch
from
679c0db
to
56e4d2b
Compare
renovate
bot
changed the title
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/reach-ui-monorepo
branch
from
56e4d2b
to
8f9b8e2
Compare
renovate
bot
force-pushed
the
renovate/reach-ui-monorepo
branch
from
8f9b8e2
to
2d007b2
Compare
renovate
bot
force-pushed
the
renovate/reach-ui-monorepo
branch
from
2d007b2
to
3f4de44
Compare
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
This PR contains the following updates:
^0.17.0->^0.18.0^0.17.0->^0.18.0Release Notes
reach/reach-ui (@reach/skip-nav)
v0.18.0Compare Source
Minor Changes
BREAKING Changes
reach-<pkg>.mjsinstead ofreach-<pkg>.esm.js.Minor Changes
We have simplified our build setup to remove a boatload of dependencies. Build output for all packages may look slightly different, though functionally packages that don't have explicit changes marked in the release notes have not changed.
This may affect you if you use
patch-packageto modify output code. If you need support for legacy browsers, the new bundle may not transpile the same ECMA features as before. In that case you may want to transpile Reach packages directly.We no longer check that our internal styles are included by looking for a defined CSS custom property. You can still include our base styles as before, but this removes the need to define
--reach-<pkg>in your own stylesheets to silence dev warnings.Patch Changes
@reach/polymorphic@0.18.0reach/reach-ui (@reach/utils)
v0.18.0Compare Source
BREAKING Changes
reach-<pkg>.mjsinstead ofreach-<pkg>.esm.js.useCheckStylesexportPolymorphictypes that were previously exported from@reach/utilshave been moved to a separate package@reach/polymorphic. As@reach/utilsis an internal package, this [breaking] change should not affect you [if you listened to us and did not use the package directly].Minor Changes
We have simplified our build setup to remove a boatload of dependencies. Build output for all packages may look slightly different, though functionally packages that don't have explicit changes marked in the release notes have not changed.
This may affect you if you use
patch-packageto modify output code. If you need support for legacy browsers, the new bundle may not transpile the same ECMA features as before. In that case you may want to transpile Reach packages directly.Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about these updates again.
This PR has been generated by Mend Renovate. View repository job log here.