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

create-neon

v0.6.0

Published

Create Neon projects with no build configuration.

Downloads

156

Readme

Create Neon

The create-neon tool bootstraps Neon projects, which allows developers to build binary Node modules written in Rust.

Usage

You can conveniently use this tool with the npm init syntax:

Creating a Simple Project

To create a simple Neon project that consists purely of Rust code:

$ npm init neon[@latest] -- [<opts> ...] my-project

Note: The initial -- is necessary for npm init to pass any command-line options to Neon.

Note: The @latest ensures that npm uses the latest version of this tool.

Global Options

-y|--yes  Skip interactive `npm init` questionnaire.

Creating a Portable Library

Neon also makes it easy to create portable, cross-platform libraries by publishing pre-built binaries. This means you can implement your Node.js library in Rust and publish the binaries so that users of your library (and any downstream users of theirs!) on all major hardware and operating systems can take a dependency on your library---without having to install Rust or run any builds.

To create a portable npm library with pre-built binaries:

$ npm init neon[@latest] -- [<opts> ...] --lib [<lib-opts> ...] my-project

Note: The initial -- is necessary for npm init to pass any command-line options to Neon.

This will generate a project that can be used by pure JavaScript or TypeScript consumers without them even being aware of the use of Rust under the hood. It achieves this by publishing pre-built binaries for common Node platform architectures that are loaded just-in-time by a JS wrapper module.

This command generates the necessary npm and CI/CD configuration boilerplate to require nearly zero manual installation on typical GitHub-hosted repos. The only manual step required is to configure GitHub Actions with the necessary npm access token to enable automated publishing.

This command chooses the most common setup by default, but allows customization with fine-grained configuration options. These configuration options can also be modified later with the Neon CLI.

Library Options

--ci none|github       CI/CD provider to generate config for.
                       (Default: github)
--bins none|npm[:org]  Cache provider to publish pre-built binaries.
                       (Default: npm, with org inferred from package)
--platform <platform>  Binary platform to add support to this library for.
                       This option can be specified multiple times.
                       (Default: macos, linux, windows)