Security News
require(esm) Backported to Node.js 20, Paving the Way for ESM-Only Packages
require(esm) backported to Node.js 20, easing the transition to ESM-only packages and reducing complexity for developers as Node 18 nears end-of-life.
github-automated-repos
Advanced tools
Github-automated-repos is the lib that gives you the power to manage the view of your projects on your website in one place!
Github-automated-repos is the lib that gives you the power to manage the visualization of your projects on the website,
in your own GitHub in one place!
https://github-automated-repos.vercel.app
npm install github-automated-repos
# or
yarn add github-automated-repos
hook config.
import {useGithubAutomatedRepos} from "github-automated-repos";
const data = useGithubAutomatedRepos("GitHubUsername", "KeyWord");
This library automates the view your GitHub projects on your website in one place. But how? Make the code configuration only once in your application with github-automated-repos, and manage the view of your projects on GitHub in the Topics field. Choose which project will be seen on your website, and you can even customize your project card, for example, with a representative icon and show which stacks were used. All in one place!
Control your projects |
---|
Customize and represent through icons. |
---|
In one place |
---|
import { useGithubAutomatedRepos, ProjectIcon, StackIcon } from 'github-automated-repos/index';
useGithubAutomatedRepos
hook responsible for automating the repositories. It returns a function called dataGithubRepos, which takes two parameters: data (data that comes from the GitHub API) and the keyword (the latter responsible for showing the project on your website from the moment it is declared in the Topics field of the your Github repository). The dataGithubRepos returns, so optimized, an array of objects containing 6 properties: id, html_url, homepage, topics, name and description.
const data = useGithubAutomatedRepos("GitHubUsername", "KeyWord");
StackIcons
component returns, based on the iteration of the topics array, icons of the stacks used in your project. Insert the stacks used in the topics field of your repository. Check the Stack Icons tab!
<StackIcons key={ } itemTopics={ } className={ } />
StackLabels
component returns, based on the iteration of the topics array, labels of the stacks used in your project. Insert the stacks used in the topics field of your repository. Check the Stack Icons tab!
<StackLabes key={ } itemTopics={ } className={ } />
ProjectIcons
component returns, based on the iteration of the topics array, icons to represent your project. The project tag must be inserted in the topics field of your repository. Check the Project Icons tab!
<ProjectIcons key={ } itemTopics={ } className={ } />
id
: repository identification number. used as parameter in the key tag. This field does not need to be filled in.html_url
: repository link. Used as the link of access. This field does not need to be filled in.homepage
: it's the access link to the built page, page deploy. About / Website of your GitHub.topics
: array that brings information about the icons in Project Icons and Stack Icons. Used in both ProjectIcon and StackIcon components. It is in this field that is passed the key configured in the hook. Refers to the field About / Topics of your GitHub.name
: This is the name of the repository. Refers to the field Settings / General / Repository name of your GitHub.description
: This is the description given to your repository. Refers to the About /Description field of your GitHub.:exclamation::exclamation: Don't forget to fill in the fields: your GitHubUsername and keyWord (determined by you).
const data = useGithubAutomatedRepos("GitHubUsername", "KeyWord");
import './App.css';
import { useGitHubAutomatedRepos, ProjectIcons, StackIcons, StackLabels, } from 'github-automated-repos';
function App() {
{/*useGithubAutomatedRepos hook*/ }
const data = useGitHubAutomatedRepos("GitHubUsername", "KeyWord");
return (
<div className="App">
{
data.map((item) => {
return (
<div key={item.id}>
{/*Project Icons*/}
{item.topics.map((icon) => {
return (
<ProjectIcons key={icon} className="project_Icon" iconItem={icon} />
)
})}
{/*html Url*/}
<a href={item.html_url}>
{/*Name Project*/}
<h1>{item.name}</h1>
</a>
{/*Description*/}
<p>{item.description}</p>
{/*Homepage*/}
<a href={item.homepage}>
<h3>Homepage</h3>
</a>
{/*Stacks Icon and Stacks Label*/}
{item.topics.map((icon) => {
return (
<div key={icon} style={{display:'flex', justifyContent:'center'}}>
<StackIcons key={icon} className="stack_Icon" itemTopics={icon} />
<StackLabels key={icon} itemTopics={icon} />
</div>
)
})}
</div>
)
})
}
</div>
);
}
export default App;
└── My-app
├── ...
├── next.config.js
├── ...
/** @type {import('next').NextConfig} */
const nextConfig = {
reactStrictMode: true,
transpilePackages: ['github-automated-repos'],
}
module.exports = nextConfig
Love github-automated-repos? Give our repo a star ⭐ ⬆️.
by
: @digoarthur
FAQs
The library, ReactJS, that gives you the power to control / automate your GitHub data, your projects on the portfolio / website, in your own GitHub in one place!
The npm package github-automated-repos receives a total of 0 weekly downloads. As such, github-automated-repos popularity was classified as not popular.
We found that github-automated-repos 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
require(esm) backported to Node.js 20, easing the transition to ESM-only packages and reducing complexity for developers as Node 18 nears end-of-life.
Security News
PyPI now supports iOS and Android wheels, making it easier for Python developers to distribute mobile packages.
Security News
Create React App is officially deprecated due to React 19 issues and lack of maintenance—developers should switch to Vite or other modern alternatives.