Components on Producthunt daily

folly

Sun, 14 Sep 2025 15:25:34 +0800

facebook/folly

Folly: Facebook Open-source Library

What is `folly`?

Folly (acronymed loosely after Facebook Open Source Library) is a library of C++17 components designed with practicality and efficiency in mind. Folly contains a variety of core library components used extensively at Facebook. In particular, it’s often a dependency of Facebook’s other open source C++ efforts and place where those projects can share code.

It complements (as opposed to competing against) offerings such as Boost and of course std. In fact, we embark on defining our own component only when something we need is either not available, or does not meet the needed performance profile. We endeavor to remove things from folly if or when std or Boost obsoletes them.

Performance concerns permeate much of Folly, sometimes leading to designs that are more idiosyncratic than they would otherwise be (see e.g. PackedSyncPtr.h, SmallLocks.h). Good performance at large scale is a unifying theme in all of Folly.

Check it out in the intro video

Logical Design

Folly is a collection of relatively independent components, some as simple as a few symbols. There is no restriction on internal dependencies, meaning that a given folly module may use any other folly components.

All symbols are defined in the top-level namespace folly, except of course macros. Macro names are ALL_UPPERCASE and should be prefixed with FOLLY_. Namespace folly defines other internal namespaces such as internal or detail. User code should not depend on symbols in those namespaces.

Physical Design

At the top level Folly uses the classic “stuttering” scheme folly/folly used by Boost and others. The first directory serves as an installation root of the library (with possible versioning a la folly-1.0/), and the second is to distinguish the library when including files, e.g. #include <folly/FBString.h>.

The directory structure is flat (mimicking the namespace structure), i.e. we don’t have an elaborate directory hierarchy (it is possible this will change in future versions). The subdirectory experimental contains files that are used inside folly and possibly at Facebook but not considered stable enough for client use. Your code should not use files in folly/experimental lest it may break when you update Folly.

The folly/folly/test subdirectory includes the unittests for all components, usually named ComponentXyzTest.cpp for each ComponentXyz.*. The folly/folly/docs directory contains documentation.

What’s in it?

Because of folly’s fairly flat structure, the best way to see what’s in it is to look at the headers in top level folly/ directory. You can also check the docs folder for documentation, starting with the overview.

Folly is published on GitHub at https://github.com/facebook/folly.

Build Notes

Because folly does not provide any ABI compatibility guarantees from commit to commit, we generally recommend building folly as a static library.

folly supports gcc (5.1+), clang, or MSVC. It should run on Linux (x86-32, x86-64, and ARM), iOS, macOS, and Windows (x86-64). The CMake build is only tested on some of these platforms; at a minimum, we aim to support macOS and Linux (on the latest Ubuntu LTS release or newer.)

`getdeps.py`

This script is used by many of Meta’s OSS tools. It will download and build all of the necessary dependencies first, and will then invoke cmake etc to build folly. This will help ensure that you build with relevant versions of all of the dependent libraries, taking into account what versions are installed locally on your system.

It’s written in python so you’ll need python3.6 or later on your PATH. It works on Linux, macOS and Windows.

The settings for folly’s cmake build are held in its getdeps manifest build/fbcode_builder/manifests/folly, which you can edit locally if desired.

Dependencies

If on Linux or MacOS (with homebrew installed) you can install system dependencies to save building them:

# Clone the repo
git clone https://github.com/facebook/folly
# Install dependencies
cd folly
sudo ./build/fbcode_builder/getdeps.py install-system-deps --recursive

If you’d like to see the packages before installing them:

./build/fbcode_builder/getdeps.py install-system-deps --dry-run --recursive

On other platforms or if on Linux and without system dependencies getdeps.py will mostly download and build them for you during the build step.

Some of the dependencies getdeps.py uses and installs are:

a version of boost compiled with C++14 support.
googletest is required to build and run folly’s tests.

Build

This script will download and build all of the necessary dependencies first, and will then invoke cmake etc to build folly. This will help ensure that you build with relevant versions of all of the dependent libraries, taking into account what versions are installed locally on your system.

getdeps.py currently requires python 3.6+ to be on your path.

getdeps.py will invoke cmake etc.

# Clone the repo
git clone https://github.com/facebook/folly
cd folly
# Build, using system dependencies if available
python3 ./build/fbcode_builder/getdeps.py --allow-system-packages build

It puts output in its scratch area:

installed/folly/lib/libfolly.a: Library

You can also specify a --scratch-path argument to control the location of the scratch directory used for the build. You can find the default scratch install location from logs or with python3 ./build/fbcode_builder/getdeps.py show-inst-dir.

There are also --install-dir and --install-prefix arguments to provide some more fine-grained control of the installation directories. However, given that folly provides no compatibility guarantees between commits we generally recommend building and installing the libraries to a temporary location, and then pointing your project’s build at this temporary location, rather than installing folly in the traditional system installation directories. e.g., if you are building with CMake you can use the CMAKE_PREFIX_PATH variable to allow CMake to find folly in this temporary installation directory when building your project.

If you want to invoke cmake again to iterate, there is a helpful run_cmake.py script output in the scratch build directory. You can find the scratch build directory from logs or with python3 ./build/fbcode_builder/getdeps.py show-build-dir.

Run tests

By default getdeps.py will build the tests for folly. To run them:

cd folly
python3 ./build/fbcode_builder/getdeps.py --allow-system-packages test

`build.sh`/`build.bat` wrapper

build.sh can be used on Linux and MacOS, on Windows use the build.bat script instead. Its a wrapper around getdeps.py.

Build with cmake directly

If you don’t want to let getdeps invoke cmake for you then by default, building the tests is disabled as part of the CMake all target. To build the tests, specify -DBUILD_TESTS=ON to CMake at configure time.

NB if you want to invoke cmake again to iterate on a getdeps.py build, there is a helpful run_cmake.py script output in the scratch-path build directory. You can find the scratch build directory from logs or with python3 ./build/fbcode_builder/getdeps.py show-build-dir.

Running tests with ctests also works if you cd to the build dir, e.g. (cd $(python3 ./build/fbcode_builder/getdeps.py show-build-dir) && ctest)

Finding dependencies in non-default locations

If you have boost, gtest, or other dependencies installed in a non-default location, you can use the CMAKE_INCLUDE_PATH and CMAKE_LIBRARY_PATH variables to make CMAKE look also look for header files and libraries in non-standard locations. For example, to also search the directories /alt/include/path1 and /alt/include/path2 for header files and the directories /alt/lib/path1 and /alt/lib/path2 for libraries, you can invoke cmake as follows:

1
2
3

cmake \
  -DCMAKE_INCLUDE_PATH=/alt/include/path1:/alt/include/path2 \
  -DCMAKE_LIBRARY_PATH=/alt/lib/path1:/alt/lib/path2 ...

Ubuntu LTS, CentOS Stream, Fedora

Use the getdeps.py approach above. We test in CI on Ubuntu LTS, and occasionally on other distros.

If you find the set of system packages is not quite right for your chosen distro, you can specify distro version specific overrides in the dependency manifests (e.g. https://github.com/facebook/folly/blob/main/build/fbcode_builder/manifests/boost ). You could probably make it work on most recent Ubuntu/Debian or Fedora/Redhat derived distributions.

At time of writing (Dec 2021) there is a build break on GCC 11.x based systems in lang_badge_test. If you don’t need badge functionality you can work around by commenting it out from CMakeLists.txt (unfortunately fbthrift does need it)

Windows (Vcpkg)

Note that many tests are disabled for folly Windows builds, you can see them in the log from the cmake configure step, or by looking for WINDOWS_DISABLED in CMakeLists.txt

That said, getdeps.py builds work on Windows and are tested in CI.

If you prefer, you can try Vcpkg. folly is available in Vcpkg and releases may be built via vcpkg install folly:x64-windows.

You may also use vcpkg install folly:x64-windows --head to build against main.

macOS

getdeps.py builds work on macOS and are tested in CI, however if you prefer, you can try one of the macOS package managers

Homebrew

folly is available as a Formula and releases may be built via brew install folly.

You may also use folly/build/bootstrap-osx-homebrew.sh to build against main:

`1`	`./folly/build/bootstrap-osx-homebrew.sh`

This will create a build directory _build in the top-level.

MacPorts

Install the required packages from MacPorts:

  sudo port install \
    boost \
    cmake \
    gflags \
    git \
    google-glog \
    libevent \
    libtool \
    lz4 \
    lzma \
    openssl \
    snappy \
    xz \
    zlib

Download and install double-conversion:

  git clone https://github.com/google/double-conversion.git
  cd double-conversion
  cmake -DBUILD_SHARED_LIBS=ON .
  make
  sudo make install

Download and install folly with the parameters listed below:

  git clone https://github.com/facebook/folly.git
  cd folly
  mkdir _build
  cd _build
  cmake ..
  make
  sudo make install

lowcode-engine

Thu, 19 Jun 2025 15:30:24 +0800

alibaba/lowcode-engine

packages/engine/README.md

react-bits

Sun, 08 Jun 2025 15:27:19 +0800

DavidHDev/react-bits

The largest & most creative library of animated React components.

Documentation

Go to reactbits.dev to view the documentation.

About

React Bits is a large collection of animated React components made to spice up your web creations. We’ve got animations, components, backgrounds, and awesome stuff that you won’t be able to find anywhere else - all free for you to use! These components are all enhanced with customization options as props, to make it easy for you to get exactly what you need.

Key Features

60 total components (text animations, animations, components, backgrounds), growing every day
All components are lightweight, with minimal dependencies, and highly customizable
Designed to integrate seamlessly with any modern React project
Each component comes in 4 variants, to keep everyone happy:
- JS + CSS
- JS + Tailwind CSS
- TS + CSS
- TS + Tailwind CSS

CLI ()

React Bits uses jsrepo for installing components via CLI.
The setup steps can be found on each component’s page in the documentation.

How To Contribute?

Contributions are welcome! Check the Open Issues to see how you can help or submit ideas using the Feature Request template.
Please review the Contribution Guide and follow our standards. Thanks for your time!

Contributors

Maintainers

David Haz

Stats

License

Licensed under the MIT license.

mui-x

Mon, 02 Jun 2025 15:32:29 +0800

mui/mui-x

MUI X

MUI X is a suite of advanced React UI components for a wide range of complex use cases. Each component provides best-in-class UX and DX, with sophisticated UX workflows for data-rich applications. Components include the Data Grid, Date and Time Pickers, Charts, and Tree View.

MUI X extends the core functionality of Material UI, but the advanced components also stand on their own and can be fully customized to meet the needs of any design system.

MUI X is open-core: Community components are MIT-licensed and free forever, while more advanced features and components require a Pro or Premium commercial license. See Licensing for more information.

Documentation

Get started in the MUI X documentation.

Installation

Licensing

The MUI X team has been building MIT-licensed React components since 2014, starting with Material UI, and we’re committed to the continued advancement of our open-source libraries. Anything we release under an MIT license will remain MIT-licensed forever. Learn more about our stewardship ethos.

We offer commercial licenses to developers who need the most advanced components and features that can’t reasonably be maintained by the open-source community alone. These licenses make it possible for us to support a full-time staff of engineers.

Rest assured that when we release features commercially, it’s only because we believe you won’t find a better MIT-licensed alternative anywhere else.

See the Licensing page for complete details.

Plans

Community plan

The free Community version of MUI X contains components and features that we believe are maintainable by contributions from the open-source community. It’s published under an MIT license and it’s free forever.

Pro plan

MUI X Pro expands on the Community version with more advanced features and functionality. The Data Grid Pro comes with multi-filtering, multi-sorting, column resizing, and column pinning; you also gain access to the Date and Time Range Picker components, advanced Charts, and drag-and-drop reordering for the Tree View.

The Pro version is available under a commercial license—visit the Pricing page for details.

Premium plan

MUI X Premium unlocks the most advanced features of the Data Grid, including row grouping and Excel exporting, as well as everything offered in the Pro plan.

The Premium version is available under a commercial license—visit the Pricing page for details.

@mui/x-data-grid-premium

Support

From community guidance to critical business support, we’re here to help. Read the Support guide for details.

Contributing

Read the Contributing guide to learn about our development process, how to propose bug fixes and improvements, and how to build and test your changes.

Contributing to MUI X is about more than just issues and pull requests! There are many other ways to support MUI X beyond contributing to the code base.

Changelog

The changelog is regularly updated to reflect what’s changed in each new release.

Roadmap

Future plans and high-priority features and enhancements can be found in the roadmap.

Security

For details on supported versions and contact information for reporting security issues, please refer to the security policy.

ant-design

Fri, 30 May 2025 15:30:47 +0800

ant-design/ant-design

Ant Design

An enterprise-class UI design language and React UI library.

Changelog · Report Bug · Request Feature · English · 中文

❤️ Sponsors and Backers

✨ Features

🌈 Enterprise-class UI designed for web applications.
📦 A set of high-quality React components out of the box.
🛡 Written in TypeScript with predictable static types.
⚙️ Whole package of design resources and development tools.
🌍 Internationalization support for dozens of languages.
🎨 Powerful theme customization based on CSS-in-JS.

🖥 Environment Support

Modern browsers
Server-side Rendering
Electron

Edge	Firefox	Chrome	Safari	Electron
Edge	last 2 versions	last 2 versions	last 2 versions	last 2 versions

📦 Install

`1`	`npm install antd`

`1`	`yarn add antd`

`1`	`pnpm add antd`

`1`	`bun add antd`

🔨 Usage

import { Button, DatePicker } from 'antd';

export default () => (
  <>
    <Button type="primary">PRESS ME</Button>
    <DatePicker placeholder="select date" />
  </>
);

🔗 Links

⌨️ Development

Use opensumi.run, a free online pure front-end dev environment.

Or clone locally:

$ git clone git@github.com:ant-design/ant-design.git
$ cd ant-design
$ npm install
$ npm start

Open your browser and visit http://127.0.0.1:8001, see more at Development.

🤝 Contributing

Let’s build a better antd together.

We warmly invite contributions from everyone. Before you get started, please take a moment to review our Contribution Guide. Feel free to share your ideas through Pull Requests or GitHub Issues. If you’re interested in enhancing our codebase, explore the Development Instructions and enjoy your coding journey! :)

For collaborators, adhere to our Pull Request Principle and utilize our Pull Request Template when creating a Pull Request.

Issue funding

We use Issuehunt to up-vote and promote specific features that you would like to see and implement. Check our backlog and help us:

angular

Fri, 30 May 2025 15:30:26 +0800

angular/angular

Angular - The modern web developer's platform

Angular is a development platform for building mobile and desktop web applications
using TypeScript/JavaScript and other languages.

angular.dev

Contributing Guidelines · Submit an Issue · Blog

Documentation

Get started with Angular, learn the fundamentals and explore advanced topics on our documentation website.

Advanced

Local Development

To contribute to the Angular Docs, check out the Angular.dev README

Development Setup

Prerequisites

Install Node.js which includes Node Package Manager

Setting Up a Project

Install the Angular CLI globally:

`1`	`npm install -g @angular/cli`

Create workspace:

`1`	`ng new [PROJECT NAME]`

Run the application:

1
2

cd [PROJECT NAME]
ng serve

Angular is cross-platform, fast, scalable, has incredible tooling, and is loved by millions.

Quickstart

Get started in 5 minutes.

Ecosystem

Changelog

Learn about the latest improvements.

Upgrading

Check out our upgrade guide to find out the best way to upgrade your project.

Contributing

Contributing Guidelines

Read through our contributing guidelines to learn about our submission process, coding rules, and more.

Want to Help?

Want to report a bug, contribute some code, or improve the documentation? Excellent! Read up on our guidelines for contributing and then check out one of our issues labeled as help wanted or good first issue.

Code of Conduct

Help us keep Angular open and inclusive. Please read and follow our Code of Conduct.

Community

Join the conversation and help the community.

Love Angular? Give our repo a star :star: :arrow_up:.

react-native

Fri, 30 May 2025 15:30:06 +0800

facebook/react-native

React Native

Learn once, write anywhere:
Build mobile apps with React.

Getting Started · Learn the Basics · Showcase · Contribute · Community · Support

React Native brings React’s declarative UI framework to iOS and Android. With React Native, you use native UI controls and have full access to the native platform.

Declarative. React makes it painless to create interactive UIs. Declarative views make your code more predictable and easier to debug.
Component-Based. Build encapsulated components that manage their state, then compose them to make complex UIs.
Developer Velocity. See local changes in seconds. Changes to JavaScript code can be live reloaded without rebuilding the native app.
Portability. Reuse code across iOS, Android, and other platforms.

React Native is developed and supported by many companies and individual core contributors. Find out more in our ecosystem overview.

📋 Requirements

React Native apps may target iOS 15.1 and Android 7.0 (API 24) or newer. You may use Windows, macOS, or Linux as your development operating system, though building and running iOS apps is limited to macOS. Tools like Expo can be used to work around this.

🎉 Building your first React Native app

Follow the Getting Started guide. The recommended way to install React Native depends on your project. Here you can find short guides for the most common scenarios:

📖 Documentation

The full documentation for React Native can be found on our website.

The React Native documentation discusses components, APIs, and topics that are specific to React Native. For further documentation on the React API that is shared between React Native and React DOM, refer to the React documentation.

The source for the React Native documentation and website is hosted on a separate repository, @facebook/react-native-website.

🚀 Upgrading

Upgrading to new versions of React Native may give you access to more APIs, views, developer tools, and other goodies. See the Upgrading Guide for instructions.

React Native releases are discussed in this discussion repo.

👏 How to Contribute

The main purpose of this repository is to continue evolving React Native core. We want to make contributing to this project as easy and transparent as possible, and we are grateful to the community for contributing bug fixes and improvements. Read below to learn how you can take part in improving React Native.

Good First Issues

We have a list of good first issues that contain bugs which have a relatively limited scope. This is a great place to get started, gain experience, and get familiar with our contribution process.

Discussions

Larger discussions and proposals are discussed in @react-native-community/discussions-and-proposals.

📄 License

React Native is MIT licensed, as found in the LICENSE file.

nue

Sun, 06 Apr 2025 15:24:51 +0800

nuejs/nue

packages/nuekit/README.md

Components on Producthunt daily

folly

Folly: Facebook Open-source Library

What is folly?

Check it out in the intro video

Logical Design

Physical Design

What’s in it?

Build Notes

getdeps.py

Dependencies

Build

Run tests

build.sh/build.bat wrapper

Build with cmake directly

Finding dependencies in non-default locations

Ubuntu LTS, CentOS Stream, Fedora

Windows (Vcpkg)

macOS

Homebrew

MacPorts

lowcode-engine

react-bits

Documentation

About

Key Features

CLI ()

How To Contribute?

Contributors

Maintainers

Stats

License

mui-x

MUI X

Documentation

Installation

Licensing

Plans

Community plan

Pro plan

Premium plan

Support

Contributing

Changelog

Roadmap

Security

ant-design

Ant Design

❤️ Sponsors and Backers

✨ Features

🖥 Environment Support

📦 Install

🔨 Usage

🔗 Links

⌨️ Development

🤝 Contributing

Issue funding

angular

Angular - The modern web developer's platform

Documentation

Advanced

Local Development

Development Setup

Prerequisites

Setting Up a Project

Quickstart

Ecosystem

Changelog

Upgrading

Contributing

Contributing Guidelines

Want to Help?

Code of Conduct

Community

react-native

Getting Started · Learn the Basics · Showcase · Contribute · Community · Support

Contents

📋 Requirements

🎉 Building your first React Native app

📖 Documentation

What is `folly`?

`getdeps.py`

`build.sh`/`build.bat` wrapper