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

apply-publishconfig

v1.1.0

Published

Apply package.json publishConfig

Downloads

1,763

Readme

apply-publishconfig

NPM version NPM downloads Release Workflow Status (with event) Tests Workflow Status (with event)

Quickly apply a publishConfig into a dependency package.json for deployment

Overview

This package will apply a publishConfig in-place to a project. I have thrown this solution together to build Node server applications with Turborepo internal packages, whilst maintaining the full local development experience. I found a PR that suggests that this feature is implemented into pnpm deploy, but it wasn't working on my end. This was built with Turborepo in mind, but there's no reason why it cannot also be used in other contexts.

Related discussions:

  • https://github.com/vercel/turbo/discussions/4509
  • https://github.com/vercel/turbo/discussions/6751

Running the script will edit the internal package's package.json in-place and will apply the publishConfig. Supported fields include main and exports

diff --git a/package.json b/package.json
index f3df0d5..a49f857 100644
--- a/package.json
+++ b/package.json
@@ -3,7 +3,7 @@
   "version": "1.0.0",
-  "main": "./src/index.ts",
+  "main": "./dist/index.js",
   "types": "./src/index.ts",
   "scripts": {
     "build": "tsup src/index.ts",
@@ -16,9 +16,6 @@
-  "publishConfig": {
-    "main": "./dist/index.js"
-  },

Usage

Install the package using your package manager:

$ pnpm add -D apply-publishconfig

Add a script to your internal package's package.json with a publishConfig:

"main": "./src/index.ts",
"types": "./src/index.ts",
"scripts": {
  "publish:apply": "apply-publishconfig"
},
"publishConfig": {
  "main": "./dist/index.js"
},

Add a pipeline to your root turbo.json:

{
  "$schema": "https://turbo.build/schema.json",
  "pipeline": {
    "publish:apply": {
      "cache": false
    }
  }
}

Now when building your app, you can execute the publish:apply pipeline:

$ turbo run publish:apply

Docker example

...

RUN --mount=type=bind,source=.git,target=.git \
    turbo run build -F "${WORKSPACE}"... \
    && turbo run publish:apply -F "${WORKSPACE}"...

RUN --mount=type=cache,id=pnpm,target=/pnpm/store \
    pnpm deploy -F "${WORKSPACE}" --prod deployed

...