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

@flowplayer/playback-prettier-config

v0.0.1

Published

Shared prettier configuration made by the Playback team

Downloads

32

Readme

@flowplayer/playback-prettier-config

This project provides a shared Prettier configuration for use across internal projects within the Playback team. It ensures consistent code formatting for JS/TS files in CI pipelines and local development.

Table of Contents

Installation

You can install this configuration as a development dependency in your project by running:

yarn add -D @flowplayer/playback-prettier-config

or

npm install -D @flowplayer/playback-prettier-config

Usage

After installation, you can use this Prettier configuration by referencing it in your project's config files.

Using prettier.config.js

You can import and extend the configuration in your project's prettier.config.js or prettier.config.cjs by adding the following:

// prettier.config.js
import config from '@flowplayer/playback-prettier-config'

export default {
  ...config,
  // Add any project-specific overrides here
}

Using package.json

Alternatively, reference it in your package.json:

{
  "prettier": "@flowplayer/playback-prettier-config"
}

Configuration Details

The shared configuration currently includes the following rules:

  • trailingComma: "es5"
  • tabWidth: 2
  • semi: false
  • singleQuote: true

For more configuration options, refer to Prettier's documentation.

Contributing

Contributions are welcome! Please submit a pull request or open an issue if you have suggestions or improvements.

Publishing

This repository is configured with a GitHub Actions workflow, defined in the publish.yml file, to automatically publish the package to npm.

How It Works

  • The workflow is triggered every time a new GitHub release is created in the repository.
  • The workflow runs on ubuntu-latest, checks out the code, sets up Node.js with version 20.x, and uses the associated npm registry URL.
  • It uses yarn to install dependencies and publish the package to npm. Note that for Yarn version 1, the script uses yarn publish.

Prerequisites

  • Ensure that you have the necessary secrets configured in your GitHub repository settings:
    • NPM_TOKEN: This should be an npm token with permission to publish to your desired npm scope or account.

Steps to Publish

  1. Create a new release in your GitHub repository with the desired version tag.
  2. Once the release is published, the GitHub Action will automatically run and publish the package to npm using the provided npm registry URL.