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

@curve-technology/webapp-scripts

v0.0.12

Published

Tooling, configuration and build-related scripts for Curve web apps

Downloads

72

Readme

Installation

Install @curve-technology/webapp-scripts and its peerDependencies

yarn add --dev @curve-technology/webapp-scripts jest eslint

Babel

To use this config, create an .babelrc file in the root of your package and add:

{
  "extends": "@curve-technology/webapp-scripts/babel/nextjs"
}

ESLint

There are four eslint configs available, pick the one most appropriate for your project:

  • JS: for general purpose usage ./node_modules/@curve-technology/webapp-scripts/eslint/eslint-js
  • React: extends the base, for use with React ./node_modules/@curve-technology/webapp-scripts/eslint/eslint-js-react
  • Typescript: extends the base, for use with Typescript ./node_modules/@curve-technology/webapp-scripts/eslint/eslint-ts
  • Typescript + React: extends the base, for use with Typescript and React ./node_modules/@curve-technology/webapp-scripts/eslint/eslint-ts-react

To use this config, create an .eslintrc file in the root of your package and reference one of the mentioned config options.

Base Typescript and React .eslintrc

Using a configuration file

The extends property value can be an absolute or relative path to a base configuration file. ESLint resolves a relative path to a base configuration file relative to the configuration file that uses it.

Example of a configuration file in JSON format:

{
  "extends": [
    "./node_modules/@curve-technology/webapp-scripts/eslint/eslint-ts-react"
  ],
  "rules": {
    "eqeqeq": "warn"
  }
}

Jest

This config assumes you're using jest.

To use this config, create an jest.config.js file in the root of your package and add:

Using the default config

module.exports = {
  ...require('@curve-technology/webapp-scripts/jest'),
}

Overriding the default config

If you need to add or override this config, use something like this:

const jestConfig = require('@curve-technology/webapp-scripts/jest')

// add an item to `setupFilesAfterEnv`
jestConfig.setupFilesAfterEnv.push('<rootDir>src/testUtils/mocks.js')

module.exports = Object.assign(jestConfig, {
  // your overrides here
  testPathIgnorePatterns: ['/dist/', '/node_modules/'],
  setupFiles: ['dotenv/config'],
  snapshotSerializers: ['jest-emotion'],
})

Prettier

To use this config, create an .prettierrc.js file in the root of your package and add:

module.exports = {
  ...require('@curve-technology/webapp-scripts/prettier'),
}

Husky

To use this config, create an .huskyrc.js file in the root of your package and add:

module.exports = {
  ...require('@curve-technology/webapp-scripts/husky'),
}

Commitlint

To use this config, create an .commitlintrc.js file in the root of your package and add:

module.exports = {
  ...require('@curve-technology/webapp-scripts/commitlint'),
}

TypeScript

To use this config, create an tsconfig.json file in the root of your repo and add:

{
  "extends": "@curve-technology/webapp-scripts/tsconfig/tsconfig.base",
  "exclude": ["node_modules", "./.storybook/**/*"],
  "include": ["next-env.d.ts", "src/**/*.ts", "src/**/*.tsx"]
}

Lighthouse

To use this config, create an lighthouserc.js file in the root of your repo and add:

module.exports = {
  ci: {
    ...require('@curve-technology/webapp-scripts/lighthouse'),
  },
}

Made by Curve's web scientists 👨‍🔬