{"repo":"frontendnetwork/veganify","free":true,"listed":false,"github":"https://github.com/frontendnetwork/veganify","clone":"git clone https://github.com/frontendnetwork/veganify.git","description":"Veganify is a modern webapp that allows you to easily scan EAN barcodes to check if a product is vegan-friendly. With a database of over 3 million products, you can quickly find out if your favorite foods and products are suitable for a vegan diet.","language":"TypeScript","stars":66,"topics":["scanner","barcode","html5","javascript","vegan","vegan-ingredients","vegan-dishes","nutrition-information","nutrition","nutrition-services"],"license":"MIT","category":"databases-storage","readme_excerpt":"Veganify Check if a product is vegan or not with » Veganify.app Overview Veganify checks the barcode (EAN or UPC) of a food- or non-food-product and tells you if it is vegan or not. It is an useful tool for vegans and vegetarians - Developed with usability and simplicity in mind, so without distracting irrelevant facts or advertising. Veganify combines the Databases of OpenFoodFacts, OpenBeautyFacts and Open EAN Database, as well as our very own ingredient checker in one tool. See an example of how it works! The Veganify Ingredients API checks the products ingredients against a list of thousands of non-vegan items. Open PWA in browser Product page on FrontEndNetwork Use the API iOS Shortcut Uptime Status Developer Guide [!TIP] We're using Conventional Commits for commit messages. Please follow this convention when making changes. Prerequisites - Node.js 20 or later - pnpm (enabled via corepack) To enable pnpm using corepack: Getting Started 1. Clone the repository: 2. Install dependencies & start dev server: Project Structure Development Commands Development Guidelines [!NOTE] We're aware not everything in this repo follows those standards. This is because of how the project was started and evolved. We're working on improving this. Component Structure - Break down components into smaller, reusable pieces - Each significant component should have its own directory with the following structure: - hooks/ for component-specific hooks - utils/ for component-specific utilities - mod","default_branch":null,"files":null,"tree":[],"storefront":"/r/frontendnetwork","claimed":false,"request_supported":{"post":"https://gitbuyer.com/r/frontendnetwork/veganify/request-supported","requests":0},"note":"indexed from public GitHub; nothing is for sale on this page. Clone it from GitHub. Paid listings live at /search."}