npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

esy-peasy

v0.0.5

Published

Esy-Peasy: Simple Esy Project Builder With Almost No Configuration

Downloads

3

Readme

esy-peasy

  • Easiest way to make native Reason programs and libraries.
  • Merlin and LSP integration out of the box.
  • For a project named my-project, produces single sharable library named my-project and a single executable named MyProject.

Build An Example:

npm install -g esy@next
git clone [email protected]:jordwalke/esy-peasy-starter.git
esy install
esy build

Make It Your Own Package:

  • Change the name field in the package.json and rebuild.

How Are The Binary And Library Built?

  • The single .re file in bin/ becomes the MyProject executable.
  • The contents of lib/ becomes the my-project named library.
  • Your binary .re file can automatically see the my-project library as the YourProjectLib module.
  • Packages that depend on your package can then use your my-project library, which then allows them to see the YourProjectLib module.

Testing The Binary:

Use the standard esy x any-command-here command to run any-command-here as if you had installed the package. For example esy x YourPackage --args builds and runs your YourPackage executable with arguments.

Customize:

  • Omit the lib/ directory if everything fits into the single file in bin/.
  • You may rename the bin/Index.re file to be bin/YourProjectNameCamelCased.re.

Adding New Package Dependencies:

  • esy add @opam/dep-name@version automatically builds and adds a new dependency to package.json.
  • Find the name of the library inside of that new package by running esy ls-libs.
  • Add that library name to package.json like this: "peasyLibs": ["the-library-name"].
  • Use that library in your code and run esy build.

Note: After adding/building a new dependency you can use esy ls-modules to see which named modules become available to you by adding the peasyLibs entry.

Publish Prebuilt binaries of your executables to npm.

Use esy to make prebuilt binary releases of your program that can be installed from plain npm.

esy release bin
cd _release/bin-darwin
npm publish --tag darwin

Tradeoffs:

esy-peasy is good for rapidly making new small executables/libraries. Once they grow, you'll want to "eject out" of esy-peasy and begin customizing using a more advanced build system.