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

@turnkeyvr/common-types

v2.42.1

Published

Typings and interfaces for common TurnKey domain objects.

Downloads

136

Readme

common-types

An npm package that contains common types and interfaces to be used throughout TurnKey applications.

Structure

This library is structured using 2 major assumptions:

  • Objects that are never meant to be instantiated will be declared as Types
  • Objects that are meant to be implemented (such as by a class) will be declared as Interfaces

Types that represent Salesforce objects are represented by appending SF to the object type (ie, the RentalSF type represents the Opportunity__c object as it exists in Salesforce).

Classes that are built from these Salesforce types have more UI-friendly field names and, in some cases, manipulate the data from Salesforce when an object is created. These should be represented by an Interface in this library and implemented in the consuming application.