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

@gasbuddy/web-coconfig

v2.0.0

Published

Default Node.js configuration files for GasBuddy projects

Readme

@gasbuddy/web-coconfig

main CI

npm version

Default Node.js configuration files for GasBuddy web projects. Uses coconfig to create a pile of configuration files.

v2.0.0: GB-services v23 web TypeScript baseline (webpack + babel SSR React apps)

As of v2.0.0, this package targets the gb-services v23 web stack: server-rendered React apps built with webpack 5 + @gasbuddy/gb-web-app v3 and compiled through Babel (not tsc emit, and not Next.js -- Next apps should stay on @gasbuddy/coconfig directly, or a future Next-specific variant). designer-web is the reference/adoption target this config is designed to match.

On top of @gasbuddy/coconfig's base, @gasbuddy/web-coconfig's v2.0.0:

  • Overrides tsconfig.json for a mixed JS/TS, no-emit setup: noEmit: true (Babel does the real build; tsc --noEmit is a type-check-only gate), allowJs: true / checkJs: false, moduleResolution: 'node', lib: ['ES2022', 'DOM', 'DOM.Iterable'], jsx: 'react-jsx', resolveJsonModule, skipLibCheck, forceConsistentCasingInFileNames, and include/exclude scoped to src, tests, types, .storybook (not the base's __tests__/__mocks__/coconfig.ts, which are this package's own dev conventions, not a web app's).
  • Emits a new types/web-globals.d.ts with ambient module declarations for *.css (CSS Modules, Record<string, string> default export), *.svg/*.png/*.gif/*.jpg (asset imports, string default export), and an interim @gasbuddy/react-components + @gasbuddy/react-components/reset.css shim (marked TODO(remove when @gasbuddy/react-components ships .d.ts) -- tracked separately).
  • Extends .eslintrc.js from @gasbuddy/eslint-config-gasbuddy-web (not the base's plain gasbuddy) and adds an override widening the test/story file glob to **/*.{test,spec,stories}.{js,jsx,ts,tsx}, since the upstream web eslint config's own override only covers .js/.jsx.
  • Does not emit next.config.js (dropped -- this is the non-Next baseline).
  • Does not emit jest.config.js (suppressed -- web apps own a two-tier Jest setup, jsdom unit tests + node integration tests via @gasbuddy/service-tester's webJestConfig, which the single base ts-jest config would collide with).

Using this package (opt-in)

Like the base @gasbuddy/coconfig, this only runs on postinstall if the consuming app wires it up. In your app's package.json:

{
  "config": {
    "coconfig": "@gasbuddy/web-coconfig"
  },
  "scripts": {
    "postinstall": "yarn dlx -p @gasbuddy/web-coconfig -p coconfig coconfig"
  },
  "dependencies": {
    "@gasbuddy/web-coconfig": "^1.3.0"
  }
}

If you need to modify the emitted configuration further, create a coconfig.js (not .ts -- see the base coconfig README for why) in your app root that imports this package's default export, tweaks it, and re-exports the result; point config.coconfig at that file instead.