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

@cloudux/ca

v1.1.9

Published

A tool for building web app without painful configuration

Downloads

41

Readme

CA

A tool for building web app without painful configuration

Quick Start

ca new react demo -d
# It will create a react app named demo and setup configuration for you
# no more webpack/babel/eslint/others configuration is need.

Install

using npm:

npm install --global @cloudux/ca

After installation, you can use ca in your command line

How to use

Create a new app

  • Create a React app: ca new react react_app

  • Create a Vue app: ca new vue vue_app

  • Create a simple web app(no mvvm framework default): ca new es6 es6_app

  • Create a es5 app: ca new es5 es5_app

  • Create a app and auto run git initialization and start dev mode: ca new vue demo -d -g

Then, cd into your app directory, and run npm run dev, it just work:)

Run npm run build will output production ready files to ./dist folders.

Run npm run generate-eslint-config will generate custom ./.eslintrc file current folder.

Run npm run generate-config will generate all config files in current folder, then you can change it whatever you like.

The created app only contains dependencies it really need(such as react/vue.js/etc), no more webpack/eslint/babel/etc dev dependencies any more.

Life is too short, goodbye to endless configuration.

Run a app

  • Run a Vue app: ca run vue

  • Run a React app: ca run react

  • Run a es6 app: ca run es6

  • Run a es5 app: ca run es5

  • Default entry point for app is src/index.js, if this is not the case for you, you can pass entry point to run command like this: ca run vue ./index.js

Build a app

  • Build a Vue app: ca build vue

  • Build a React app: ca build react

  • Build a ES6 app: ca build es6

  • Build a ES5 app: ca build es5

  • Default entry point for app is src/index.js, if this is not the case for you, you can pass entry point to run command like this: ca build vue ./index.js

  • The build files will output to ./dist folders

Generate Custom ESLint configuration files

  • ca generate vue eslint

Then ca will generate a .eslintrc file in current project's folder, then change the config if you like. However, don't forget to add all the config's dependencies to dev dependencies.

Generate Custom configuration files

  • ca generate vue all

Then ca will generate all config files in current project's folder, then change the config if you like. However, don't forget to add all the config's dependencies to dev dependencies.