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

angular-compiler-components

v1.8.0

Published

Projeto para compilar componentes angulares

Downloads

10

Readme

Build Status dependencies Status devDependencies Status semantic-release npm version codecov Commitizen friendly Greenkeeper badge

angular-compiler-components

Angular compiler components é um projeto para compilar componentes em angular. Baseado no angular-library-builder

What is Angular Library Builder (nglb)?

It's a CLI Tool to build Angular (2+) libraries ready to be published to npm.

What problem is Angular Library Builder (nglb) trying to solve?

At the moment there is no official documentation/guidelines on how to build and publish Angular (2+) components/libraries/services/modules to npm. Angular Library Builder (nglb) is trying to solve this in the easiest way possible.

How does Angular Library Builder (nglb) solve this?

  1. If it is a component, inlines html template file into the component as a string, replacing templateUrl with template
    • In the inlining process nglb also minifies html using html-minifier
  2. If it is a component, inlines scss/sass/css file(s) into the component as a string, replacing stylesUrls with styles. It uses:
  3. Finally, it compiles your resulting typescript files with all your html and css inlined, using @angular/compiler-cli (ngc), creating *.d.ts, *.js, *.js.map, *.metadata.json files

Getting Started

Install the angular-compiler-components command

npm install --save-dev angular-compiler-components

How to use angular-compiler-components?

Add angular-compiler-components (nglb) script, main and types to package.json:

"main": "./lib-dist/your-main-file.js",
"types": "./lib-dist/your-main-file.d.ts",
"scripts": {
  "build:library": "nglb --rootDir src/lib --outDir lib-dist"
}

or

"main": "./lib-dist/your-main-file.js",
"types": "./lib-dist/your-main-file.d.ts",
"scripts": {
  "build:library": "angular-compiler-components --rootDir src/lib --outDir lib-dist"
}

Now, in your project root:

npm run build:library

Congratulations! Your library is available in lib-dist folder ready to be published to npm.

To publish your new library to npm, execute the following command in your project root:

npm publish

Options that angular-compiler-components supports

option (argument) | description ------------ | ------------- --rootDir | Specifies the root directory of input files. Example: nglb --rootDir src, [required] --outDir | Redirect output structure to the directory. Example: nglb --outDir dist, [required] --tsconfig | Possibility to extend/override properties in default tsconfig-ngc.json. Example: nglb --tsconfig path/to/your/override-tsconfig-ngc.json --help (-h) | Print help message

How to change angular-compiler-components tsconfig-ngc.json default properties?

Sometimes the defaults aren't good enough for everybody.

Example

Let's imagine that you want to change slightly the build process:

  1. change the default "target" from "es5" to "es2015"
  2. add a new property, for example, "noImplicitAny": true,

To acomplish this create a file called, for example, override-tsconfig-ngc.json in your project root. Your override-tsconfig-ngc.json file can be something like:

{
  "compilerOptions": {
    "target": "es2015",
    "noImplicitAny": true
  }
}

Then, you invoke nglb like this:

nglb --rootDir path/to/your/source --outDir path/to/dist --tsconfig override-tsconfig-ngc.json

Authors and Contributors

@bmvantunes (Bruno Antunes, author)

Special thanks to gulp-inline-ng2-template. Without gulp-inline-ng2-template angular-compiler-components would not be possible!

License

The repository code is open-sourced software licensed under the MIT license.