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

@in-human-resources/backend-proto

v0.1.27

Published

Protobuf-ES and Connect-ES generated clients for api.v1, auth.v1, hiring.v1, workflow.v1, assessment.v1, and common.v1

Readme

@in-human-resources/backend-proto

Published npm package: Protobuf-ES message types and Connect-ES service stubs for api.v1, auth.v1, and common.v1.

Install

npm install @in-human-resources/backend-proto@^0.1.9

The package ships compiled ESM under gen/ts/dist/ (run npm run build in this folder before publish or when using file: link).

Monorepo / local dev:

"@in-human-resources/backend-proto": "file:../Backend/proto"

Then from Backend/proto: npm install && npm run build, and reinstall in your app.

Next.js (optional): compiled .js exports usually work without transpilePackages. If you hit resolution issues, add:

transpilePackages: ["@in-human-resources/backend-proto"],

Imports (unchanged):

import { AuthService } from "@in-human-resources/backend-proto/gen/ts/api/v1/auth_connect";

Peer dependencies (install in your app):

npm install @bufbuild/protobuf @connectrpc/connect

For browsers you may also use @connectrpc/connect-web.

Usage

Import Connect service definitions and create a client (example: gateway api.v1):

import { createClient } from '@connectrpc/connect';
import { createGrpcTransport } from '@connectrpc/connect-node';
import { AuthService } from '@in-human-resources/backend-proto/gen/ts/api/v1/auth_connect';

const transport = createGrpcTransport({ baseUrl: 'http://localhost:8082', httpVersion: '2' });
export const authClient = createClient(AuthService, transport);

Use the same pattern for company_connect, candidate_connect, or internal auth/v1/service_connect (extensionless so Next/Turbopack can resolve the published .ts files).

Note: Code is generated with import_extension=none so local imports inside gen/ts omit .js. The package only publishes TypeScript under gen/ts (not precompiled .js); a .js suffix in import specifiers is incorrect for that layout.

Source .proto files (contract reference)

The package ships the original Protobuf schemas next to generated code so you can read RPCs and messages without leaving node_modules:

| Location in the package | Contents | |-------------------------|----------| | api/v1/*.proto | Public gateway API (AuthService, CompanyService, CandidateService, HiringService, shared types) | | auth/v1/service.proto | Internal auth service (auth.v1.AuthService) | | hiring/v1/service.proto | Private hiring service (hiring.v1.HiringService) | | common/v1/common.proto | Shared common.v1 messages |

Example path after install:

node_modules/@in-human-resources/backend-proto/api/v1/auth.proto

buf.yaml / buf.gen.yaml are included for Buf-based tooling if you point at this folder as a module.

Regenerate (maintainers)

From the repository root:

(cd proto && npm ci) # first time or after dependency changes
make proto-gen

This refreshes Go output under gen/ and TypeScript under gen/ts/. Commit both when APIs change.

Version history

0.1.27

  • Regenerated Go and TypeScript clients (buf generate).

0.1.26

  • Additive: AssessmentAssignmentSummarycompany_name, job_title, languages, application_stage (api.v1 + assessment.v1).
  • Additive: Jobcandidate_has_applied, profile_match_percent (api.v1; gateway-populated).
  • Additive: GetJobResponsecandidate_has_applied, profile_match_percent (api.v1; gateway-populated for candidates).
  • Additive: Applicationnext_action_label, next_action_due_at (api.v1; gateway-populated).

0.1.12

  • Additive: CreateJobRequest.team_metadata_json (field 5) on api.v1 and hiring.v1 for role team context on create (department, location, employment type, etc. as JSON).

0.1.11

  • Prior published baseline (pipeline types, hiring surface).

Publish

  1. Bump "version" in package.json.

  2. npm login (npmjs.com account with permission to publish the @in-human-resources scope).

  3. npm requires 2FA to publish (or a granular access token with publish rights). Enable 2FA on npm account settings (Authorization and publishing), or create a token with “Bypass two-factor authentication” if your org allows it.

  4. From proto/:

    npm publish

    publishConfig.access is set to public in package.json for this scoped package.

What ships on npm

| Path | Contents | |------|----------| | gen/ts/ | Generated TypeScript (*_pb.ts, *_connect.ts) | | api/, auth/, hiring/, common/ | Source .proto files (API contract) | | buf.yaml, buf.gen.yaml | Buf module + codegen config |

Go stubs under gen/*.go are not published (they stay in the git repo for the backend workspace only).