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

ng4-test-pkg

v0.0.2

Published

A ng4 test module to check if it builds well with ng4 projects

Downloads

5

Readme

ng4-test-pkg

Build Status

Build an Angular library compatible with AoT compilation & Tree shaking.

This starter allows you to create a library for Angular 4+ apps written in TypeScript, ES6 or ES5. The project is based on the official Angular packages.

Get the Changelog.

Contents

1 Project structure

  • Library:
    • src folder for the classes
    • public_api.ts entry point for all public APIs of the package
    • package.json npm options
    • rollup.config.js Rollup configuration for building the bundles
    • tsconfig-build.json ngc compiler options for AoT compilation
    • build.js building process using ShellJS
  • Testing:
    • tests folder for unit & integration tests
    • karma.conf.js Karma configuration that uses webpack to build the tests
    • spec.bundle.js defines the files used by webpack
  • Extra:
    • tslint.json TypeScript linter rules with Codelyzer
    • travis.yml Travis CI configuration

2 Customizing

  1. Update Node & npm.

  2. Rename ng4-test-pkg and ng4TestPkg everywhere to my-library and myLibrary.

  3. Update in package.json file:

    and run npm install.

  4. Create your classes in src folder, and export public classes in my-library.ts.

  5. You can create only one module for the whole library: I suggest you create different modules for different functions, so that the user can import only those he needs and optimize Tree shaking of his app.

  6. Update in rollup.config.js file globals external dependencies with those that actually you use.

  7. Create unit & integration tests in tests folder, or unit tests next to the things they test in src folder, always using .spec.ts extension. Karma is configured to use webpack only for *.ts files.

3 Testing

The following command run unit & integration tests that are in the tests folder, and unit tests that are in src folder:

npm test 

4 Building

The following command:

npm run build
  • starts TSLint with Codelyzer
  • starts AoT compilation using ngc compiler
  • creates dist folder with all the files of distribution

To test locally the npm package:

npm run pack-lib

Then you can install it in an app to test it:

npm install [path]my-library-[version].tgz

5 Publishing

Before publishing the first time:

npm run publish-lib

6 Documentation

To generate the documentation, this starter uses compodoc:

npm run compodoc
npm run compodoc-serve 

7 Using the library

Installing

npm install my-library --save 

Loading

Using SystemJS configuration

System.config({
    map: {
        'my-library': 'node_modules/my-library/bundles/my-library.umd.js'
    }
});

Angular-CLI

No need to set up anything, just import it in your code.

Rollup or webpack

No need to set up anything, just import it in your code.

Plain JavaScript

Include the umd bundle in your index.html:

<script src="node_modules/my-library/bundles/my-library.umd.js"></script>

and use global ng.myLibrary namespace.

AoT compilation

The library is compatible with AoT compilation.

8 What it is important to know

  1. package.json

    • "main": "./bundles/ng4-test-pkg.umd.js" legacy module format
    • "module": "./bundles/ng4-test-pkg.es5.js" flat ES module, for using module bundlers such as Rollup or webpack: package module
    • "es2015": "./bundles/ng4-test-pkg.js" ES2015 flat ESM format, experimental ES2015 build
    • "peerDependencies" the packages and their versions required by the library when it will be installed
  2. tsconfig.json file used by TypeScript compiler

    • Compiler options:
      • "strict": true enables TypeScript strict master option
  3. tsconfig-build.json file used by ngc compiler

    • Compiler options:

      • "declaration": true to emit TypeScript declaration files
      • "module": "es2015" & "target": "es2015" are used by Rollup to create the ES2015 bundle
    • Angular Compiler Options:

      • "skipTemplateCodegen": true, skips generating AoT files
      • "annotateForClosureCompiler": true for compatibility with Google Closure compiler
      • "strictMetadataEmit": true without emitting metadata files, the library will not compatible with AoT compilation
  4. rollup.config.js file used by Rollup

    • format: 'umd' the Universal Module Definition pattern is used by Angular for its bundles
    • moduleName: 'ng.ng4TestPkg' defines the global namespace used by JavaScript apps
    • external & globals declare the external packages
  5. Server-side prerendering

    If you want the library will be compatible with server-side prerendering:

    • window, document, navigator and other browser types do not exist on the server
    • don't manipulate the nativeElement directly

Built with this starter

License

MIT