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

fisx-command-install

v0.2.0

Published

component install for fisx

Downloads

8

Readme

fisx-command-install

Dependency Status devDependency Status NPM Version

Install component package command for fisx.

How to use

Install specified package

fisx install er # install the latest version, using the default endpoint
fisx install echarts@^2.0.0 # specify the version information
fisx install ecomfe/[email protected] # install component from github
fisx install github:ecomfe/[email protected] # is equivalent to previous commad, specify the endpoint
fisx install edp:er # install component from edp registry
fisx install npm:jquery # install component from npm
fisx install gitlab:fis-components/jquery # install component from gitlab
fisx install moye2=ecomfe/moye # specify the alias name `moye2`
fisx install https://codeload.github.com/jquery/jquery/legacy.zip/3.0.0-alpha1 # install from url
fisx intall ./xx/mypackage.zip # install from local
fisx install npm:etpl --registry http://registry.npm.baidu.com # specify custom registry
fisx install npm:react --registry http://registry.npm.taobao.org # using the custom registry

By default, the component package information will always save to dependencies of package.json.

If not specify the endpoint, it'll use the default edp endpoint. If you wanna change the default endpoint, using the component.defaultEndPoint configure item:

fis.set('component.defaultEndPoint', {type: 'github', value: 'ecomfe'});
fis.set('component.defaultEndPoint', {type: 'npm'}); // default using `http://registry.npmjs.org`
fis.set('component.defaultEndPoint', {type: 'npm', value: '<your default registry>'});

If using gitlab, some custom options you can configure:

fis.set('component.defaultGitlabDomain', 'http://<your gitlab domain>');
fis.set('component.defaultGitlabToken', '<private token>');

The private token information, you can refer here. By default the private token value will be read from environment variable GITLAB_TOKEN.

Init project dependence

fisx install # install all deps and devdeps specified in `package.json`
fisx install --production # only install dependencies, exclude devdependencies

View help information

fisx install -h