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 🙏

© 2025 – Pkg Stats / Ryan Hefner

@ionic/angular

v8.7.14

Published

Angular specific wrappers for @ionic/core

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

gm-osgm-osionicjsionicjs

Keywords

ionicframeworkangularmobileappwebappcapacitorcordovaprogressive web apppwa

Readme

@ionic/angular

Ionic Angular specific building blocks on top of @ionic/core components.

Related

License

Testing Local Ionic Framework with ng add

This guide shows you how to test the local Ionic Framework build with a new Angular application using ng add. This is useful for development and testing changes before publishing.

Prerequisites

  • Node.js and npm installed
  • Angular CLI installed globally (npm install -g @angular/cli)

Build Local Ionic Framework

  1. Clone the repository (if not already done):

    git clone https://github.com/ionic-team/ionic-framework.git
cd ionic-framework

  2. Pull the latest from main

    git pull origin main

  3. Install dependencies and build the core package:

    cd core
npm install
npm run build

  4. Install dependencies, sync the core build and build the Angular package:

    cd ../packages/angular
npm install
npm run sync
npm run build

  5. Create a tarball:

    cd dist
npm pack

  6. Copy the tarball to Downloads:

    cp ionic-angular-*.tgz ~/Downloads/ionic-angular.tgz

Test with New Angular App

  1. Create a new Angular app:

    # Change to whichever directory you want the app in
cd ~/Documents/
ng new my-app --style=css --ssr=false --zoneless=false
cd my-app

  2. Install the local @ionic/angular package:

    npm install ~/Downloads/ionic-angular.tgz

  3. Run ng add:

    ng add @ionic/angular --skip-confirmation

  4. Serve the app:

    ng serve

The local Ionic Framework build is now active in the Angular app. Changes to the Ionic source code require rebuilding the packages and reinstalling the tarball to see updates.

Project Structure

common

This is where logic that is shared between lazy loaded and standalone components live. For example, the lazy loaded IonPopover and standalone IonPopover components extend from a base IonPopover implementation that exists in this directory.

Note: This directory exposes internal APIs and is only accessed in the standalone and src submodules. Ionic developers should never import directly from @ionic/angular/common. Instead, they should import from @ionic/angular or @ionic/angular/standalone.

standalone

This is where the standalone component implementations live. It was added as a separate entry point to avoid any lazy loaded logic from accidentally being pulled in to the final build. Having a separate directory allows the lazy loaded implementation to remain accessible from @ionic/angular for backwards compatibility.

Ionic developers can access this by importing from @ionic/angular/standalone.

src

This is where the lazy loaded component implementations live.

Ionic developers can access this by importing from @ionic/angular.