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

@quenty/nevermoreclimanifest

v1.10.1

Published

Manifest of nevermore CLI-injected deploy metadata (commit, target, version, timestamp)

Readme

NevermoreCliManifest

Manifest of nevermore CLI-injected deploy metadata (commit, target, version, timestamp)

Installation

npm install @quenty/nevermoreclimanifest --save

Usage

When a place is deployed with nevermore deploy, the CLI finds this package's NevermoreCLIManifestUtils ModuleScript in the built place and writes the deployment metadata onto it as attributes. Because the data rides on the package's own instance it replicates to clients automatically, so any consumer can read it from either the client or the server:

local NevermoreCLIManifestUtils = require("NevermoreCLIManifestUtils")

local metadata = NevermoreCLIManifestUtils.getGameMetadata()
if metadata.deployed then
	print(string.format("%s @ %s (%s)", metadata.target, metadata.commit, metadata.timestamp))
else
	print("Undeployed build (Studio)")
end

getGameMetadata() returns a GameMetadata table:

| Field | Type | Description | | --- | --- | --- | | deployed | boolean | true only when injected by a nevermore deploy (false in Studio) | | commit | string? | Short git commit SHA | | version | string? | Full git commit SHA | | branch | string? | Git branch the build was made from | | target | string? | Deploy target name (e.g. "test", "integration") | | timestamp | string? | ISO 8601 UTC time of the deploy | | published | boolean? | true if published live (--publish), false if only Saved | | placeId | number? | Roblox place ID deployed to | | universeId | number? | Roblox universe ID deployed to | | basePlaceId | number? | Roblox place ID of the base place this build merged from | | basePlaceVersion | number? | Version of that base place the build was made from |

basePlaceVersion is the only record of which upstream Studio content a build contains: a "published" base place pin resolves at deploy time and the base place keeps moving afterwards, so it cannot be recovered later. Both base place fields are absent on a build that merged none.

Use NevermoreCLIManifestUtils.observeGameMetadata() for an Observable that fires the current snapshot and again whenever a field changes (for example when the metadata first replicates to a client), or isDeployed() for a quick boolean check.

If a place does not depend on this package, the CLI finds no injection point and the deploy proceeds unchanged.