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

property-wize-types

v2.0.25

Published

Define data types for front end and backend

Downloads

1,566

Readme

Using property-wize-types Project's Type Definitions

The property-wize-types project is a library for defining types for frontend and middleware projects. You can add new type files under the src/types folder of the property-wize-types project. After adding a new type file, run the npm run generate-index command to generate the index.ts file. Then, run npx tsc command to compile the project.

In the other two projects, dependencies to the property-wize-types project have been configured, and after compilation, you can use the newly added types in these two projects.

Steps

  1. Add New Type Definitions: Add the new type file to the src/types folder of the property-wize-types project.

  2. Generate index.ts File: Run the following command to generate the index.ts file:

npm run generate-index

  1. Compile the Project: Run the following command to compile the project:

npx tsc

  1. Use in Other Projects: Dependencies to the property-wize-types project have already been configured in the other two projects. You can directly import and use the newly added types.

Example

Suppose you have added a new type file named NewType.ts to the src/types folder. Follow these steps:

  1. Define the new type in the NewType.ts file.
  2. Run npm run generate-index to generate the index.ts file.
  3. Run npx tsc to compile the project.
  4. Import and use the NewType type in the other projects.
// Importing the newly added type in other projects
import { NewType } from 'property-wize-types';

Publish the property-wize-types Project manually

After adding new type definitions and compiling the project, you can publish the property-wize-types project to npm. Run the following command to publish the project:

./publish -v -p

This will update the version and publish the property-wize-types project to npm with the version specified in the package.json file.

Before you can do this, need to run npm login on the commandline window to login to npm. This will redirect to the webpage, where you can enter your username and password. After logging in, you can run the publish command to publish the project.

Publish the property-wize-types Project automatically

Run the following script to update the version only.

./publish -v

Once the changes is pushed or merged into dev branch. Github workflow will automatically publish the package.