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

@lugamafe/nx-biome

v0.0.2-2

Published

This library was generated with [Nx](https://nx.dev).

Downloads

4

Readme

nx-biome

This library was generated with Nx.

Building

Run nx build nx-biome to build the library.

Running unit tests

Run nx test nx-biome to execute the unit tests via Jest.

Usage

Format Command

You can use the format executor with the following options:

# Basic usage
nx format yourProjectName

# With write flag to apply changes
nx format yourProjectName --write

# With unsafe flag to allow unsafe operations
nx format yourProjectName --unsafe

# Combine both flags
nx format yourProjectName --write --unsafe

Lint Command

Similarly for the lint command:

# Basic usage
nx lint yourProjectName

# With write flag to apply fixes
nx lint yourProjectName --write

# With unsafe flag
nx lint yourProjectName --write --unsafe

Check Command

For check command:

# Basic usage
nx check yourProjectName

# With write and unsafe flags
nx check yourProjectName --write --unsafe

Overriding Default Flags

If an executor has --write or --unsafe flags configured as true by default in your project configuration, you can override them using the --no-write or --no-verify flags:

# Override default write=true configuration
nx format yourProjectName --no-write

# Override default unsafe=true configuration
nx lint yourProjectName --no-verify

# Override both default configurations
nx check yourProjectName --no-write --no-verify

Default Executor Configuration Example

Here's an example of how an executor might be configured with default flags in your project.json file:

{
  "projects": {
    "your-project": {
      "targets": {
        "format": {
          "executor": "@lugamafe/nx-biome:format",
          "options": {
            "write": true,
            "unsafe": true
          }
        },
        "lint": {
          "executor": "@lugamafe/nx-biome:lint",
          "options": {
            "write": true
          }
        }
      }
    }
  }
}

With this configuration, the format command would run with both --write and --unsafe enabled by default, and you would need to use --no-write or --no-verify to disable them.