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

yarn-lock-to-package-json

v0.3.1

Published

[![npm](https://img.shields.io/npm/v/yarn-lock-to-package-json)](https://www.npmjs.com/package/yarn-lock-to-package-json)

Downloads

502

Readme

yarn-lock-to-package-json

npm

A simple script to be used in Dockerfile to do yarn install without copying all package.jsons in a monorepo workspace. Use case inspired by pnpm's fetch command but for Yarn Berry.

Usage in Dockerfile

# ------------------------------------------------------------------------------
# First image (install dependencies)
# ------------------------------------------------------------------------------
FROM node:16-alpine as yarn
LABEL stage=yarn

WORKDIR /workspace

COPY .yarn ./.yarn
COPY yarn.lock .yarnrc.yml ./

RUN yarn dlx yarn-lock-to-package-json

RUN yarn install --immutable
# ------------------------------------------------------------------------------
# Server image (build image with production dependencies only)
# ------------------------------------------------------------------------------
FROM yarn as server
LABEL stage=server

WORKDIR /workspace

# Overwrite dummy package.json with actual ones (so that we can use scripts)
COPY package.json ./
COPY packages ./packages
COPY apps/server ./apps/server

RUN yarn workspaces foreach -tR --from @workspace-name/server run build

RUN cd apps/server && yarn workspaces focus --production

CMD ["yarn", "workspace", "@workspace-name/server", "start"]

Yarn Plugin

For similar functionality but packaged in a yarn plugin you can check out yarn-plugin-fetch by @devthejo, it uses this package internally to provide the same feature plus adds workspace focus support and more tools.

Working

What it does is parse the lockfile and recreate the monorepo structure by creating dummy package.json for each package in the workspace. These dummy package.json don't invalidate your docker cache when you change a script or increment a version and so your docker build cache remains valid up to the layer of RUN yarn install --immutable.

Test it by copying your yarn.lock to a new folder and run npx yarn-lock-to-package-json.

This is the dummy file generated:

{
  "name": "@monorepo/package",
  "version": "0.0.0",
  "description": "**DON'T COMMIT** Generated file for caching",
  "private": true,
  "dependencies": {
    "typescript": "^4.5.5"
  }
}

Motivation

These existing issues in yarn