react-balloon.css
Advanced tools
A react styled-components implementation of kazzkiq's balloon.css
A react styled-components implementation of kazzkiq's balloon.css
Simply install using npm install react-balloon.css or yarn add react-balloon.css
You can then wrap it around any component passing at least the message prop through.
import Tooltip from 'react-balloon.css';
...
<Tooltip message={'Tooltip message'}>
<ButtonComponent />
<Tooltip>
...
message[undefined]: String;
length[fit]: String (small|medium|large|xlarge|fit)
blockChild[false]: Boolean (when wrapping around block element eg: h1)
always[false]: Boolean (Always display)
position[top]: String (top|bottom|left|right)
https://github.com/RemeJuan/react-balloon.cssyarn installlib/index.jsyarn test / yarn test:watchDiscover the release history by heading on over to the releases page.
Unless stated otherwise all works are:
and licensed under:
FAQs
A react styled-components implementation of kazzkiq's balloon.css
The npm package react-balloon.css receives a total of 4 weekly downloads. As such, react-balloon.css popularity was classified as not popular.
We found that react-balloon.css demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Research
The Socket Research Team breaks down a malicious wrapper package that uses obfuscation to harvest credentials and exfiltrate sensitive data.
Research
Security News
Attackers used a malicious npm package typosquatting a popular ESLint plugin to steal sensitive data, execute commands, and exploit developer systems.
Security News
The Ultralytics' PyPI Package was compromised four times in one weekend through GitHub Actions cache poisoning and failure to rotate previously compromised API tokens.