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 🙏

© 2025 – Pkg Stats / Ryan Hefner

@crossplane-js/libs

v0.0.39

Published

Shared libraries for Crossplane XFuncJS

Readme

Skyhook Libs

This package contains shared libraries for Crossplane Skyhook.

Recent Changes

YAML Parsing in pkg/node/process.go

The code now properly parses the .yarnrc.yml file using the sigs.k8s.io/yaml library instead of string manipulation.

Direct Yarn Execution

We've improved the yarn installation process by directly executing the yarn binary from the path specified in the .yarnrc.yml file. This approach:

  1. Extracts the yarnPath from the .yarnrc.yml file
  2. Constructs the absolute path to the yarn executable
  3. Executes it directly with Node.js

Implementation Details

The Go code now:

  1. Parses the .yarnrc.yml file to extract the yarnPath value
  2. Falls back to a default path if not found
  3. Executes the yarn binary directly:
// Extract the yarnPath from the .yarnrc.yml file
var yarnPath string
if yarnConfig != nil {
    if path, ok := yarnConfig["yarnPath"].(string); ok {
        yarnPath = path
    }
}

// If yarnPath is not found, use the default yarn executable
if yarnPath == "" {
    yarnPath = ".yarn/releases/yarn-4.7.0.cjs"
}

// Construct the absolute path to the yarn executable
yarnExecPath := filepath.Join("/app", yarnPath)

// Run yarn install using the extracted yarn executable
yarnCmd := exec.Command("node", yarnExecPath, "install")
yarnCmd.Dir = uniqueDirPath // Set the working directory

This approach ensures that the yarn installation process runs in a separate process and doesn't block the main Node.js process, while also being more robust by using the exact yarn executable specified in the project configuration.