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

@codejen/pack-cpp

v1.4.3

Published

jen pack for C++: class/shader scaffolding in src/, plus SDL3 (+ OpenGL) app starters

Readme

@codejen/pack-cpp

A jen pack for modern C++: app starters (SDL3, SDL3 + OpenGL, console, library, modules), RAII and type generators following the C++ Core Guidelines, and tooling for tests, linting, profiling and packaging.

Documentation: https://learosema.github.io/jen/recipes.html – every generator with its params and the plan it prints.

Install

npm install --save-dev @codejen/pack-cpp   # or: npm install -g @codejen/jen @codejen/pack-cpp

jen picks the pack up automatically; see jen's own README for how pack discovery works.

jen cpp:sdl3 --name=MyGame
cd my-game
jen cpp:doctest
jen cpp:class --name=Camera --withTest

Where files go

Generators that scaffold a file (cpp:class, cpp:struct, cpp:interface, …) write into the current directory, or --dir. From src/net/, jen cpp:class --name=Socket writes src/net/Socket.h and wires net/Socket.cpp into the nearest CMakeLists.txt that carries the # jen:sources marker; jen cpp:class --name=Socket --dir=src/net does the same from the project root.

Wiring is looked up by marker, not guessed:

  • --withTest: the test goes next to the header and is wired into the CMakeLists.txt that carries # jen:tests.
  • No marker: without a CMakeLists.txt that carries it, the plan shows the insert as skipped. Add the marker and run the generator again – files that already exist are left alone.

Tooling generators (cpp:warnings, cpp:tidy, cpp:doctest, …) work on the project as a whole: their files (cmake/…, .clang-tidy, tests/) go to the project root, from wherever you are.

The starters (cpp:app, cpp:lib, cpp:module, cpp:sdl3, cpp:sdl3-opengl) create a new project folder in the current directory; --dir names it.

License

ISC © Lea Rosema; the vendored glad loader CC0 and its khrplatform.h MIT © The Khronos Group – see THIRD_PARTY_NOTICES.md