[Snyk] Upgrade @reach/tooltip from 0.2.2 to 0.18.0#106
Open
Conversation
Snyk has created this PR to upgrade @reach/tooltip from 0.2.2 to 0.18.0. See this package in npm: https://www.npmjs.com/package/@reach/tooltip See this project in Snyk: https://app.snyk.io/org/spoor2709/project/5c47dee4-eeef-4694-b206-fa2ce6273287?utm_source=github&utm_medium=referral&page=upgrade-pr
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 was automatically created by Snyk using the credentials of a real user.
Snyk has created this PR to upgrade @reach/tooltip from 0.2.2 to 0.18.0.
ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.
Release notes
Package name: @reach/tooltip
-
0.18.0 - 2022-10-13
- All default exports have been removed. Replace all default imports with the appropriate documented named export.
- The output directory structure has changed slightly. Module files are now named
-
-
-
0.18.0-pre.5 - 2022-10-12
-
0.18.0-pre.4 - 2022-10-12
-
0.18.0-pre.3 - 2022-10-11
-
0.18.0-pre.2 - 2022-10-11
-
0.18.0-pre.1 - 2022-10-11
-
0.18.0-pre.0 - 2022-10-11
-
0.17.0 - 2022-04-20
-
0.16.2 - 2021-10-17
-
0.16.0 - 2021-08-02
-
0.15.3 - 2021-07-10
-
0.15.2 - 2021-06-28
-
0.15.0 - 2021-04-07
-
0.14.0 - 2021-03-28
-
0.13.2 - 2021-02-21
-
0.13.1 - 2021-02-21
-
0.13.0 - 2021-01-26
-
0.12.1 - 2020-11-27
-
0.12.0 - 2020-11-26
-
0.11.2 - 2020-09-01
-
0.11.1 - 2020-09-01
-
0.11.0 - 2020-08-21
-
0.10.5 - 2020-06-24
-
0.10.4 - 2020-06-15
-
0.10.3 - 2020-05-21
-
0.10.2 - 2020-05-11
-
0.10.1 - 2020-04-22
-
0.10.0 - 2020-04-05
-
0.9.1 - 2020-03-19
-
0.9.0 - 2020-03-14
-
0.8.6 - 2020-03-06
-
0.8.5 - 2020-02-21
-
0.8.4 - 2020-02-15
-
0.8.3 - 2020-02-15
-
0.8.2 - 2020-02-08
-
0.8.0 - 2020-01-30
-
0.7.4 - 2020-01-25
-
0.7.3 - 2020-01-17
-
0.7.2 - 2020-01-10
-
0.7.0 - 2019-12-22
-
0.6.4 - 2019-12-10
-
0.6.3 - 2019-12-06
-
0.6.2 - 2019-11-23
-
0.6.1 - 2019-11-15
-
0.5.4 - 2019-11-06
-
0.5.3 - 2019-11-04
-
0.5.0 - 2019-10-31
-
0.4.0 - 2019-10-23
-
0.4.0-beta.0 - 2019-10-12
-
0.3.0 - 2019-10-11
-
0.3.0-alpha.0 - 2019-10-04
-
0.2.2 - 2019-06-19
from @reach/tooltip GitHub release notesChanges for individual packages can now be found in the
CHANGELOG.mdfile in the root of the affected package. GitHub releases will be used to document changes affecting all or several packages in the repo.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.Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information:
🧐 View latest project report
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs