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

nodecg-types

v1.9.0

Published

Types from nodecg but without all the baggage and dependencies

Downloads

117

Readme

nodecg-types

If you are developing NodeCG bundles in TypeScript you need typings for nodecg.

The official guide recommends that you import them directly from the local NodeCG installation using relative paths. This can easily break if the install NodeCG version is incorrect or the user has placed your bundle somewhere other than in nodecgInstall/bundles/yourBundle. Also your bundle cannot be compiled if you don't have NodeCG installed.

Some people require the nodecg npm package directly to get around these problems. However this pulls in all the dependencies of NodeCG into your project/node_modules directory which are tremendous in count and size. Because of this npm installs are pretty slow and also you have NodeCG stored multiple times on your disk. Once for your actual install and then one additional install for each TypeScript bundle that imports the NodeCG typings this way.

nodecg-types solves this by republishing just the official NodeCG types. It does not contain any other NodeCG code and only has the dependencies that are needed for the typings to work.

Note: this is an unofficial package and a temporary workaround till NodeCG 2.x is released! Please refer to this issue regarding how the official NodeCG typings will be handled in the future.

Usage

nodecg-types behaves the same way as the official nodecg npm package regarding types.

You install it using npm:

npm install nodecg-types --save

And then import the typings you need. The paths are completely the same meaning nodecg-types is a drop-in replacement and you can just exchange nodecg for nodecg-types:

import { NodeCG } from "nodecg-types/types/server";