@flywire/react-hooks
Advanced tools
A collection of Reacts hooks used in Flywire
Add the dependency to your package.json:
npm i @flywire/react-hooks
Install dependencies and peer dependencies:
npm install
npm install react react-dom lodash.isequal validate.js@0.11.1 xregexp --no-save
npm run test
To create a new release, make all the changes that you need and commit them, then execute:
npm version [<newversion> | major | minor | patch | premajor | preminor | prepatch | prerelease | from-git]
For example:
npm version patch
npm publish
or for a beta:
npm version prepatch
npm publish --tag beta
This will bump the package.json version, build a new bundle, commit, push the
changes tagging them to a new release.
Then create a PR and request the review from other project commiters. Once
accepted and merged to master, execute npm publish from master branch.
[1.2.0] - 2021-02-9
complete and uncomplete functions take current step as default argumentFAQs
A collection of Reacts hooks used in Flywire
The npm package @flywire/react-hooks receives a total of 348 weekly downloads. As such, @flywire/react-hooks popularity was classified as not popular.
We found that @flywire/react-hooks demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 0 open source maintainers 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.