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 🙏

© 2026 – Pkg Stats / Ryan Hefner

inline-cpp

v0.1.8

Published

Use inline C++ in your JS

Readme

NPM version NPM download GitHub issues GitHub license

inline-cpp

Inline C++ with Node.js

Works on: Linux, Windows, MacOS

Purpose:

  • Simplify native module prototyping. Enable native code in Node.js REPL.
  • Allow JS scripts to generate C++ code and run it dynamically.
  • Popularise NAPI usage and node-addon-api.
  • This is NOT intended to be used as native module replacement!
    If you want to publish a native module, please package it as required by node-gyp.

Installation

npm install --save inline-cpp

or install it globally (it works with Node.js REPL):

npm install -g inline-cpp

Usage

// test.js
const compile = require('inline-cpp');

const hello = compile `
  String func(const CallbackInfo& info) {
    return String::New(info.Env(), "Hello world from C++!");
  }
`

console.log(hello())

Now run it:

➜ node test.js
Hello world from C++!

The first time you run the script, it takes longer to execute. For each inline block of code, a native module will be generated, compiled with node-gyp and loaded dynamically. If the module Init function is not defined, it is generated as well.
The next time you run the script, it will reuse previously generated module, so it will run instantly (unless you change the inline C++ code).

For more C++ code examples, see node-addon-api
For more inline-cpp API examples, see examples on github

API

inline-cpp supports several invocation methods.

Pass some code as string to build it with default options.

const InlineCPP = require('inline-cpp');
InlineCPP('code')

You can also pass code using tagged template syntax.

InlineCPP `code`

Pass an object to create a new compiler with custom options.
Options will get passed to node-gyp target.

const customCompiler = InlineCPP({ ... })

If the code block only contains a single function, the compiler returns the function.
If it contains multiple functions or custom Init, the module itself is returned.

Disclaimer

This is just a prototype. I created this to check the general concept.
You're welcome to contribute! Here are some ideas:

  • [x] Parse/Find all functions in the block of code, add them to exports
  • [ ] Use node-gyp directly, instead of invoking node node-gyp.js
  • [ ] Improve error handling/reporting
  • [ ] Create advanced usage examples
  • [ ] Cleanup unused modules from cache periodically
  • [ ] ...

Debugging

You can enable debug output by setting env. variable: DEBUG=inline-cpp