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

brick-cli-base

v1.3.0

Published

[![npm version](https://badge.fury.io/js/brick-cli-base.svg)](https://badge.fury.io/js/brick-cli-base)

Downloads

16

Readme

brick-cli-base

npm version

♂ brick-cli-XX is a serie of packages used to organize web-front projects using templates in webpack-base-project, alonging with cli commands.

♂ purposes

  1. Organize projects with less config works, which is achieved by encapsulting basic config works into an npm package. Encapsulting also make projects's dependencies in "package.json" file more concise.

  2. Uniform basic project configs between diffenent projects using the same same framework.

  3. Update project configs more easily. Updating specific package's version will reach the goal.

♂ Related framework for each package is as follows.

| package name | framework | | :--------------------------------------------------------------: | :----------: | | brick-cli-base | no framework | | brick-cli-react | react | | brick-cli-vue | vue |

usage

♀ Install specific brick-cli-XX package.

♀ Run "brick init" for the first time. This will create config files for tools like ".eslintrc.js", "babel.config.js", ".prettierrc" and so on with default configurations. If one config file has existed, it will not be overwritten, and a message like "xxx has existed, ignore creation." will be displayed in the command window.

♀ (selectable) Run "brick tidydeps" to remove duplicated dependencies that has been included by brick-cli-XX from the project's "package.json" file. Then run "yarn install" to let yarn re-tidy the relationships between packages.

♀ Custom webpack configurations can be set in "brick.config.js" file under the project's root directory. Content of the file can be in one of three forms below.

/*
* 1.Configurations will be merged by "webpack-merge".
* 2.The "brickBase" field corresponds to configurations in "build/config.js" file of "webpack-base-project".
*/

module.exports = {
  brickBase:{
    urlPrefix: 'http://my.prefix'
  },
  devServer:{
    port: 2023
  }
}
/*
* Configurations returned by the function will be treated as the final webpack config.
*/
module.exports = (curConfig)=>{
  curConfig.devServer.port = 2023;
  return curConfig;
}
/*
* 1.Configurations returned by the first function corresponds to configurations in "build/config.js" file of "webpack-base-project".
* 2.Configurations returned by the second function will be treated as the final webpack config.
*/
module.exports = [(baseConfig)=>{
  baseConfig.urlPrefix = 'http://my.prefix';
  return baseConfig;
}, (curConfig)=>{
  curConfig.devServer.port = 2023;
  return curConfig;
}];

♀ Other configurations for ESLint, TypeScript, Vite, etc can be set in related config files.

♀ Other cli commands are listed below. It will be convenient to write them into corresponding scripts in the "package.json".

♀ PS: Commands starting with 'brick' above may require a 'npx' prefix.