greglobinski / react-custom-share

Social media share buttons for ReactJS. Use one of the built-in button themes or create a custom one from scratch.

greglobinski.com

That's the code of my website (greglobinski.com). My first production-use of the Gatsby-React tandem.

Screenshots

Build with

• Gatsby
• React

Starting point

• gatsby-starter-hello-world

Additional plugins and packages

• gatsby-plugin-postcss-sass
• gatsby-plugin-react-helmet
• gatsby-plugin-netlify
• gatsby-plugin-nprogress
• react-redux
• redux
• autoprefixer
• react-icons
• react-obfuscate
• Exo and Roboto fonts through typefaces

Setup

1. Install gatsby-cli (docs)
2. Clone the repository to your localhost
3. Install dependencies (yarn install)
4. Use gatsby-cli to start in development mode (docs)
5. Have fun.

react-custom-share's Issues

Sharing on LinkedIn

When you share a link in linkedin the longText and text props are not working...
Tested on your demo: demo

text: "Give it a try - react-custom-share component",
longtext: "Social sharing buttons for React. Use one of the build-in themes or create a custom one from the scratch.",

Thanks

New networks requests

For now react-custom-share has built-in share scripts for six 'networks':

• Facebook
• Twitter
• Google+
• Linkedin
• Pinterest
• Email

If you think that we should add a built-in share script for a new network add a comment-request here.

But first, check if someone has not requested it already. Make sure that there is not a comment- request for the network you want to add already.

If there is already a comment-request for the network, just react with a thumb-up to the comment.

Please do not replicate comment-requests for the same network. Thank you.

On Icon Click

i need OnClick event when i click on Icon

The automated release is failing 🚨

🚨 The automated release from the master branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you could benefit from your bug fixes and new features.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can resolve this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the master branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here is some links that can help you:

• Usage documentation
• Frequently Asked Questions
• Support channels

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

---

Invalid npm token.

The npm token configured in the NPM_TOKEN environment variable must be a valid token allowing to publish to the registry https://registry.npmjs.org/.

If you are using Two-Factor Authentication, make configure the auth-only level is supported. semantic-release cannot publish with the default auth-and-writes level.

Please make sure to set the NPM_TOKEN environment variable in your CI with the exact value of the npm token.

---

Good luck with your project ✨

Your semantic-release bot 📦🚀

Count For Each Social Media Button

i need and Total Count Under The Each Button that i can see all Total Count of Share My Website

Error sharing on LinkedIn

Clicking the share button for LinkedIn display the below error