0.0.0 • Published 1 year ago

iccc v0.0.0

Weekly downloads
-
License
ISC
Repository
github
Last release
1 year ago

iccc

A simple Vue UI library construction tool (At least for now, it's like this)

install

npm install  --global  iccc

use

create a new project

use you terminal and input :

npm iccc  init vue

If you install globally, you can also use the following command

iccc  init vue

If you have already decided on the name of the project, you can:

npx iccc  init <project>

If you install globally, you can also use the following command

iccc  init vue <project>

If you are lazy, you can use v instead of vue and use -i instead of init in the command. That is, the shortest (in the case of global installation) command is

iccc -i v

create a component

npx iccc create  vue

as init , you can use iccc -c v of you global install

Supplementary explanation to the working directory

After generating the project, you can cd <project name> enter the project root directory, execute npm install && npm run dev, and then you can see the initial test button component rendering test

The component uses Vue's jsx writing style, similar to template writing style

library ( component's home)

The root directory of the component, which exposes the component to the outside through index. ts. The components are located in the library folder, and you can add new components by using the command npx iccc -c v.

The npx iccc - c v command will create a new component with the name you entered in the src directory (please follow the naming convention for new components, separate words with -), and automatically add exports to library/src/index.ts. If you want to overwrite the component after writing some code, you can overwrite it again by using the command npx iccc -c v <component name>.

static

This is a component testing area where you can test newly written components that have just arrived

about css

This project uses the scss write css style. You can write styles into the .scss file under the same name of the component. Because the project was exported as an on-demand export, the css was split, but after being packaged with rollup, a magical line was generated. The current solution is to manually write references using the shell file

If you have any questions, you can directly submit question

0.0.0

1 year ago