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

@sjcrh/proteinpaint-types

v2.94.0

Published

Shared type definitions between ProteinPaint server and client code

Downloads

868

Readme

@sjcrh/proteinpaint-types

Background

This workspace was separated from the deprecated server/shared/types dir. The type definitions here are meant to used by the tsc compiler, and will not be included in runtime bundles.

Put type definitions that are used in client and server code in this workspace. Do NOT put here type definitions that are specific to one workspace, those should be saved in the applicable workspace.

Develop

IMPORTANT: When changing source code that are used to generate runtime checker code, run npm run generate after saving changes. This package script will call typia to generate runtime code from typescript markup. If there are lots of iterations in editing type definitions that could affect run time code generation, you may call npm run dev which will watch changed src files and trigger a call to typia to regenerate dist runtime code.

Consumer code can use type definitions from @sjcrh/proteinpaint-types, which maps to src/index.ts.

Consumer code may also use runtime code from @sjcrh/proteinpaint-types/checkers, which maps to

  • dist/index.js for server code in nodejs env
  • [public_dir]/dist/*.js for client code in browser environment, requires symlinking from @sjcrh/proteinpaint-types/dist to somewhere under public dir.

Note that in dev environment, tsx and esbuild are expected to directly transform dist/*.ts files for server and browser usage, respectively.

Test

npm test