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-clinical6

v3.34.122-mvp

Published

Library QuickStart package.json from the documentation, supplemented with testing support

Downloads

757

Readme

Angular Clinical 6


npm version Build Status

Requirements

  • NodeJs
  • NPM(It comes with NodeJs Installation)
  • Visual Studio Code

Folder structure

  • root
  • out-tsc(temporal folder at compilation)
  • dist-ac6(output from the compilation process)
  • src(source files)
    • app
      • angular-clinical6(NPM Angular Module files)
        • components(angular-clinical6 components)
        • services, directives, etc...
      • components(playground components)

Start Development

The first step is to install project dependencies, run the command npm install from the project folder, after finishing dependencies installation, run the command ng serve --open to run the application.

Adding a component

The ng-cli can be used to create components, not matter if them are for the angular-clinical6 package or not.

Components from angular-clinical6 are located on src/app/angular-clinical6/components/ and you can add them with the required structure for the component using the command ng g component src/app/angular-clinical6/components/{{component name or route here}}, this will add automatically a reference of the component to the module angular-clinical6, still needs to add the component to the export section of the module.

If the component class needs to be accessible from outside of the library, its required to add a file or modify if exist the index.ts and add the code export * from '{{component route}}', check index.ts files from the folder angular-clinical6 and follow the references for an example.

The same process is applied with services, directives and other components of an angular module.

Adding a playground for a component

Playgrounds are used to show component basic usage and demo, also for friendly development preview, them are just normal components declared through the main module instead angular-clinical6 module.

Playground can be created through ng-cli command ng g component components/{{route or component name}} but it must be added to the routing.module.ts manually.

Build package

Package version its defined by the version number that is stored in package.json file on the root folder of the project. Every time changes will be committed to the project repository, this version number should be increased manually, when the package its built, will generate a package from this version ready to be installed as a npm package.

The build command is npm run build.