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

@taoyage/configs

v1.3.5

Published

CLI toolbox for common scripts for my projects

Downloads

12

Readme

yg-configs 🛠📦

license npm

CLI toolbox for common scripts for my front-end projects


Table of Contents

Installation

$ npm install @taoyage/configs --save-dev
or
$ pnpm install @taoyage/configs -D

Usage

This can be a very helpful way to make editor integration work for tools like ESLint,babel,prettier,commitlint which require project-based configuration to be present to work.

config prettier

if we were to do this for prettier, you could create an .prettierrc.js with the contents of

module.exports = require('@taoyage/configs/prettier');

config eslint

if we were to do this for eslint of typescript react project, you could create an .eslintrc.js with the contents of

module.exports = require('@taoyage/configs/eslint-ts');

create tsconfig.json with the contents of

{
    "extends": "@taoyage/configs/shared-tsconfig",
    "compilerOptions": {},
    "exclude": [],
    "include": []
}

config commitlint

if were to do this for commitlint, you could create an .commitlintrc.js with the contents of

module.exports = require('@taoyage/configs/commitlint');

config lintstaged

if were to do this for lintstaged, you could create an .lintstagedrc.js with the contents of

module.exports = require('@taoyage/configs/lintstaged');

config stylelint

if were to do this for stylelint, you could create an .stylelintrc.js with the contents of

module.exports = require('@taoyage/configs/stylelint');

config postcss

if were to do this for postcss, you could create an postcss.config.js with the contents of

module.exports = require('@sk/configs/postcss');

config swc

if were to do swc-loader to webpack configure,you could import this swc configuration, this configuration suport typescript program. example of

  import swcOptions from '@taoyage/configs/swc-ts';

  module: {
    rules: [
      {
        test: /\.ts?x$/,
        use: {
          loader: 'swc-loader',
          options: swcOptions(rootPath, { isDev: false, override: {} }),
        },
      },
    ],
  },

| params | description | type | | -------- | ---------------------------- | ------ | | rootPath | tsconfig.json file path | string | | isDev | current is dev or production | bool | | override | swc compilation config | object |

config babel

if were todo babel-loader to webpack configure to react, you could create an .babelrc.js with content of

module.exports = {
    presets: [['@taoyage/configs/babel']],
};

TODO

  • [x] eslint config
  • [x] tsconfig
  • [x] prettier
  • [x] commitlint config
  • [x] lintstage config
  • [x] stylelint config
  • [x] swc config
  • [x] babel config
  • [x] browserslist