Gathering detailed insights and metrics for @giphy/react-components
Gathering detailed insights and metrics for @giphy/react-components
Gathering detailed insights and metrics for @giphy/react-components
Gathering detailed insights and metrics for @giphy/react-components
npm install @giphy/react-components
@giphy/react-components@9.8.0
Published on 05 Nov 2024
@giphy/react-components@9.7.1
Published on 01 Nov 2024
@giphy/js-util@5.2.0
Published on 29 Oct 2024
@giphy/react-components@9.7.0
Published on 29 Oct 2024
@giphy/react-components@9.6.0
Published on 05 Aug 2024
@giphy/react-components@9.5.1
Published on 01 Aug 2024
Module System
Min. Node Version
Typescript Support
Node Version
NPM Version
155 Stars
1,208 Commits
53 Forks
30 Watching
72 Branches
75 Contributors
Updated on 22 Nov 2024
Minified
Minified + Gzipped
TypeScript (87.96%)
JavaScript (6.13%)
Svelte (4.95%)
HTML (0.75%)
Shell (0.21%)
Cumulative downloads
Total Downloads
Last day
-1.8%
9,870
Compared to previous day
Last week
-2%
54,221
Compared to previous week
Last month
11.4%
239,293
Compared to previous month
Last year
27.9%
2,190,347
Compared to previous year
8
2
34
The GIPHY SDKs let you and your users easily access the world’s largest GIF library anywhere on your website. Whether it’s via a comment, forum post, review, chatbot or messenger, adding GIFs to your product is a simple and easy way to boost engagement and user experience.
Choose your flavor!
React components focused on ease-of-use and performance
lightweight UI components, no framework required
fetch gifs, stickers, categories and more (build your own UI, no SDK analytics)
This SDK sends analytics events back to GIPHY in the form of pingbacks to help us improve the quality of search results for your users.
1$ yarn
Some packages have
1$ cd packages/components 2$ yarn run dev
From root of project:
1$ yarn run lint
Publishing to npm will be done by the changeset github action.
In your pr you will create a changeset by using the changest cli. Readmore here
1$ yarn changeset
Follow the prompts to specify the semver and describe the changes you've made. This will create a changeset file which should be committed. Once you have your changeset ready and the PR is approved, you can merge your PR to master.
The github actions will run and create another PR based on your changeset. When this PR is approved and merged, the Publish github action will run and the packages will be published.
If you're not ready to publish your changeset, you don't have to merge the changeset PR
No vulnerabilities found.
No security vulnerabilities found.