1. Overview
  2. Docs
ReasonML bindings to the Heroicons React components

Install

dune-project
 Dependency

Authors

Maintainers

Sources

1.0.tar.gz
md5=3584cdc11cd907b7d6efd4aebfe0257c
sha512=294d02c342d1971c7a7db33c2586dc477395a4e6a353bde04ad15a4dda457134d7e16a813e872ce8ac05df3869e68efa9244dd4fe6220ba97c20856aed993561

Description

Tags

heroicons icons reason react

Added to opam-repository:

README

Heroicons Reason React

This is a simple project wrapping the heroicons React bindings in ReasonML.

Quick Start

To install:

opam install heroicons-reason-react
npm install @heroicons/react # Must be >= 2.2.0

Now you can include heroicons-reason-react in your libraries in the appropriate dune file and do something like:

...
<Heroicons.S16.Solid.AcademicCap
  className="some-class"
/>
...

Contributing

This is a quite simple repository, though contributions are welcome. The code to generate the wrappers all resides within the generate/ directory. Calling dune exec -- generator will create the wrapper code. Feel free to open any issues and I'll help where I can.

Dependencies (6)

  1. reason-react-ppx
  2. reason-react >= "0.15.0"
  3. melange >= "4.0.0"
  4. dune >= "3.8" & >= "3.8"
  5. reason >= "3.13.0"
  6. ocaml

Dev Dependencies (2)

  1. odoc with-doc
  2. opam-check-npm-deps with-dev-setup

Optional Dependencies

None

Used by

None

Conflicts

None

Build status

Results of building heroicons-reason-react with each compiler on check.ci.ocaml.org, run of against opam-repository 78c202b. All results for this package.

Each result links to its build log. To keep crawlers from overloading the site, build logs require a GitHub sign-in (see ocurrent/opam-health-check). On your first log, GitHub asks you to “Authorize opam-health-check”, the OCurrent app that runs these checks; it sees only your public profile, not your repositories. The sign-in lasts 30 days.

Version OCaml 4.11 OCaml 4.14 OCaml 5.2 OCaml 5.4 OCaml 5.5
1.0 (this version) n/a good good good good
  • good Package successfully built
  • partial One of the dependencies failed to build
  • bad Package failed to build
  • n/a Package is not available in this environment
  • internal Internal failure