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

ng2-lib-cli-tools

v1.3.3

Published

Add karma environment to an angular2 library

Downloads

5

Readme

Angular2 library command line tool

Making a testable library as a stand-alone application. Live debugging of typescript ( webpack ).

Install

npm install -g ng2-lib-cli-tools

Usage


  Usage: nglib [options] [command]


  Options:

    -V, --version          output the version number
    -m, --module <module>  Path to main module with new and install
    -s, --skipnpm          Skip npm commands ( install, build, test ) with new and install
    -h, --help             output usage information


  Commands:

    vscode                       Add vscode chrome launcher
    new [directory]              Create an angular2 library with karma testing environment
    install [directory]          Update or install karma testing environment in an exixting library
    i [directory]
    generate <blueprint> [name]  Create blueprints ([cl]ass, [c]omponent, [d]irective, [e]num, [g]uard, [i]nterface, [m]odule, [p]ipe, [s]ervice)
    g <blueprint> [name]

npm scripts

Build the library :

npm run build
# Build every time a file is modified
npm run build:watch

Run tests :

npm test

Consuming the library in development

my-lib is an Angular2 library

my-app is an Angular2 application who use the library

  • Add the library to npm libs

    cd to the library directory, then type :

    npm link
  • Add the link to the library

    Set up a path mapping in the application /src/tsconfig.app.json file :

    {
        "compilerOptions": {
            "paths": {
                "@angular/*": [
                    "../node_modules/@angular/*"
                ]
            }
        }
    }

    cd to the application directory, then type :

    npm link my-lib

Serve or test the application. cd to the library directory, then run the build:watch command :

npm run build:watch

Make change in a file in the library /src directory will be detected and restart the served application.

Project structure

my-lib
├── .vscode
│   └── launch.json
├── dist
├── gulp
│   ├── inline-resources.js
│   └── tsconfig.build.json
├── karma
│   ├── main.ts
│   ├── polyfills.ts
│   ├── test.ts
│   ├── tsconfig.json
│   └── tsconfig.spec.json
├── src
│   └── my-lib.module.ts
├── test
│   └── my-lib.spec.ts
├── .angular-cli.json
├── gulpfile.js
├── karma.conf.js
├── package-lock.json
├── package.json
└── tsconfig.json

src/

The library source files.

No index.ts file is required, they will be generated during the build.

test/

The test cases directory, not *.spec.ts files will be ignored.

vscode

If your project is inside a sub directory of the workspace, you have to copy the generated configuration to the root of the workspace, and define the webroot in the launch.json file :

{
    "version": "0.2.0",
    "configurations": [
        {
            "name": "Launch Chrome",
            "webRoot": "${workspaceRoot}/dir-to-library",
        },
        {
            "name": "Attach to Chrome",
            "webRoot": "${workspaceRoot}/dir-to-library"
        }
    ]
}