Huge News!Announcing our $40M Series B led by Abstract Ventures.Learn More
Socket
Sign inDemoInstall
Socket

create-neon

Package Overview
Dependencies
Maintainers
2
Versions
12
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

create-neon

Create Neon projects with no build configuration.

  • 0.5.0
  • Source
  • npm
  • Socket score

Version published
Weekly downloads
21
decreased by-38.24%
Maintainers
2
Weekly downloads
 
Created
Source

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 -- [<opts> ...] my-project

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

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 -- [<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)

Keywords

FAQs

Package last updated on 03 Jun 2024

Did you know?

Socket

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Install

Related posts

SocketSocket SOC 2 Logo

Product

  • Package Alerts
  • Integrations
  • Docs
  • Pricing
  • FAQ
  • Roadmap
  • Changelog

Packages

npm

Stay in touch

Get open source security insights delivered straight into your inbox.


  • Terms
  • Privacy
  • Security

Made with ⚡️ by Socket Inc