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-shared

v2.88.2

Published

ProteinPaint code that is shared between server and client-side workspaces

Downloads

375

Readme

@sjcrh/proteinpaint-shared

Background

This workspace was separate from the deprecated server/shared dir. The code here are meant to be consumed at runtime by either client or server code. Do NOT put utility/helper code here that are specific to only one workspace, those files should be saved in that workspace.

IMPORTANT:

  • code must work in browser and nodejs: do not import libs, deps, or globals that are specific to nodejs or browser environments, like fs or DOM elements

Develop

For server dev, the tsx library will accept imports with or without file extension. Server (consumer) code MUST use the .js file extension even when importing #shared/*.ts files.

For client dev, the esbuild config will bundle the #shared imports correctly, even when .js extension is used to import what is actually a .ts file, by using custom plugins like dirname.

Build

This package will be bundled as part of the client dependencies.

For server builds, run npm run build to generate src/*.js from src/*.ts files. This is also automatically done as part of the prepack package script.

NOTE: For now, only code in .js files. OR, if using .ts files, then commit the generated .js files, until a dev script or another approach can take care of the .js file requirement.

Test

npm test