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

node-gypcc

v0.9.4

Published

node-gyp wrapper for compiling native node addons without the binding.gyp conventions - just works with make, cmake, ninja, etc. Use it like gcc, emcc, clang, CC=node-gypcc

Downloads

20

Readme

node-gypcc

node-gyp wrapper for compiling native node addons without the binding.gyp build conventions - compat with make, cmake, ninja, etc. Use it like gcc, emcc, clang, CC=node-gypcc. Arguments & environment variables are carefully marshalled to heal gyp pain with electron, xcode_settings and rigid filesystem constraints.

  • single src file (<400 LOC)
  • single dep (node-gyp)

cli

basics:

# install
npm install -g node-gypcc

# build no binding.gyp
node-gypcc hello.c -o hello.node

# require no build/[Debug|Release}/...
node -e "require(hello.node).hello()"

more realistic build script:

# node-gyp specific cli args
CC="node-gypcc --silly --debug"

# fixes gyp inconsistencies in npm env vars
# see: https://github.com/nodejs/node-gyp/issues/2250
export npm_config_runtime="electron"
export npm_config_target="13.1.2"
export npm_config_dist_url="https://electronjs.org/headers"

# for the shell fluent >> gyp conditionals & variables
export MAKE="gmake"
CFLAGS="-I${PREFIX}/include -I${PWD}"
CFLAGS+=" -fPIC -O3 -std=c2x -pthread -Wno-incompatible-pointer-types"
CFLAGS+=" -Wno-int-conversion -Wno-error=deprecated-declarations"
if [ "$(uname)" == "Darwin" ]; then
    # marshalls magically reserved words of gyp xcode_settings
    # see: https://github.com/nickdesaulniers/node-nanomsg/pull/144
    CFLAGS+=" -mmacosx-version-min=10.12"
fi
LDFLAGS="-L${PREFIX}/lib -ltcc -lpthread"

# env or args
CFLAGS=$CFLAGS $CC $LDFLAGS ./binding.c -o ./build/binding.node

reminder software degrades faster than hardware improves:

CC=node-gypcc make binding.node

lib

WIP