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

ramdacase

v1.0.6

Published

[![NPM](https://nodei.co/npm/ramdacase.png)](https://nodei.co/npm/ramdacase/)

Downloads

15

Readme

ramdacase

NPM

Go beyond toUpper with these additional text transform functions based on Ramda.

Requires ramda as a peer dependency.

Install

npm install --save ramda ramdacase

Usage

import * as RC from "ramdacase";

const s = "The quick, brown, fox...";

// Convert to other case styles.
// (splits on whitespace, dashes, underscores, periods, & commas)
RC.toCamel(s); // "theQuickBrownFox"
RC.toPascal(s); // "TheQuickBrownFox"
RC.toKebab(s); // "The-quick-brown-fox"
RC.toKebabUpper(s); // "THE-QUICK-BROWN-FOX"
RC.toSnake(s); // "The_quick_brown_fox"
RC.toSnakeUpper(s); // "THE_QUICK_BROWN_FOX"
RC.toDot(s); // "The.quick.brown.fox"
RC.toSlash(s); // "The/quick/brown/fox"

// Use custom delimiter...
const toBreadcrumbCase = RC.toCase(" > ");
toBreadcrumbCase(s); // "The > quick > brown > fox"

RC.capitalize("the quick, brown..."); // "The quick, brown..."
RC.uncapitalize("The quick, brown..."); // "the quick, brown..."

// Only split words without rejoining them
RC.toWords(s); // ["The", "quick", "brown", "fox"]

// Split based on any delimiters...
RC.splitByAll(["&", "="])("id=1&name=mims"); // ["id", "1", "name", "mims"]
RC.splitByAll([" ", ",", "[", "]"])("[[1, 4, 7], [2, 5, 8], [3, 6, 9]]");
// ["1", "4", "7", "2", "5", "8", "3", "6", "9"]

Below this line is boilerplate from TSDX

=====

Library bootstrapped with TSDX

For more info, see tsdx.io

Commands

TSDX scaffolds your new library inside /src.

To run TSDX, use:

npm start # or yarn start

This builds to /dist and runs the project in watch mode so any edits you save inside src causes a rebuild to /dist.

To do a one-off build, use npm run build or yarn build.

To run tests, use npm test or yarn test.

Configuration

Code quality is set up for you with prettier, husky, and lint-staged. Adjust the respective fields in package.json accordingly.

Jest

Jest tests are set up to run with npm test or yarn test.

You can also use yarn test --watch or yarn test --coverage

Bundle Analysis

size-limit is set up to calculate the real cost of your library with npm run size and visualize the bundle with npm run analyze.

Rollup

TSDX uses Rollup as a bundler and generates multiple rollup configs for various module formats and build settings. See Optimizations for details.

TypeScript

tsconfig.json is set up to interpret dom and esnext types, as well as react for jsx. Adjust according to your needs.

Continuous Integration

GitHub Actions

Two actions are added by default:

  • main which installs deps w/ cache, lints, tests, and builds on all pushes against a Node and OS matrix
  • size which comments cost comparison of your library on every pull request using size-limit

Optimizations

Please see the main tsdx optimizations docs. In particular, know that you can take advantage of development-only optimizations:

// ./types/index.d.ts
declare var __DEV__: boolean;

// inside your code...
if (__DEV__) {
  console.log("foo");
}

You can also choose to install and use invariant and warning functions.

Module Formats

CJS, ESModules, and UMD module formats are supported.

The appropriate paths are configured in package.json and dist/index.js accordingly. Please report if any issues are found.

Named Exports

Per Palmer Group guidelines, always use named exports. Code split inside your React app instead of your React library.

Including Styles

There are many ways to ship styles, including with CSS-in-JS. TSDX has no opinion on this, configure how you like.

For vanilla CSS, you can include it at the root directory and add it to the files section in your package.json, so that it can be imported separately by your users and run through their bundler's loader.

Publishing to NPM

We recommend using np.