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

@duuzra/types

v2.0.14

Published

This project contains all models/types for the Duuzra application stack.

Downloads

100

Readme

Duuzra Types

This project contains all models/types for the Duuzra application stack.

Development

Environment Setup

To make life easier during development you can use the npm link functionality. This will create a symbolic link between the target and dependent projects and will save you from having to push and pull every change. It will create a dependency to a local package without modifying package.json, you will also be able to modify the files of the package directly through the dependent application.

Given a folder structure similar to this:

duuzra
    duuzra_types
        ...
    duuzra_app
        ...

navigate to the duuzra_app directory and run:

npm link ../duuzra_types

This will then create the link between the types and app projects, you can verify this by going into the node_modules folder in the app and looking for @duuzra/types. Any changes made to the types project will be immediately reflected in the app project. Obviously this is not suitable for release, the normal method of linking is required here.

To remove the link, run the following:

npm rm @duuzra/types

If the link still appears, then remove globally too:

npm rm -g @duuzra/types

Important: If you have configured the npm link, deleting the node modules folder of the dependent application will also delete the files from the linked package. Be sure to unlink the package before deleting. A good process would be to only use the npm link when actively changing the types project. As soon as the changes have been pushed to the repo, run the unlink command.

Building

The types project is configured to automatically build during install or update in the dependant project. Alternatively you can run the build manually by executing the following:

npm run build