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

@adobe/aem-core-components-angular-base

v1.0.16

Published

This module provides a Angular implementation for the [AEM core components](https://www.aemcomponents.dev/). This enables you to use the core components: -In the [AEM SPA editor](https://docs.adobe.com/content/help/en/experience-manager-64/developing/hea

Downloads

909

Readme

AEM WCM Components - Angular Core implementation

This module provides a Angular implementation for the AEM core components. This enables you to use the core components: -In the AEM SPA editor with Angular -Or in any other Angular context, provided you have the input needed to instantiate the components.

Current supported / exported components:

Page Authoring

  • Button (V1)
  • Download (V1)
  • Image (V2)
  • List (V2)
  • Separator (V1)
  • Teaser (V1)
  • Text (V2)
  • Title (V2)

Layout

  • BreadCrumb (V2)
  • Language Navigation (V1)
  • Navigation (V1)

Abstraction

  • AbstractCoreComponent
  • CoreComponentModel (interface)

Containers

For the containers (Accordion,Tabs,Carousel,Container) we do not provide any implementation in this project. It does not make sense to provide it for web-components as you can leverage the normal Core Components implementation such as a Tab Container, and drag your web components in there. Instead we provide them for the SPA editor only, introducing a dependency, and therefore we moved it into a separate project.

Usage

You can choose to import the entire library at once OR import components individually. The latter is useful if you want to only enable a few components and you want to save your javascript footprint. Also, if you want to load all core components, but you want to lazyload them with angular suspense, you will need to import them individually.

Importing the whole library:

import * as BaseCoreComponents from "@adobe/aem-core-components-angular-base";
const {ButtonV1, ButtonV1Model, ButtonV1IsEmptyFn} = BaseCoreComponents;

Importing the button component individually:

import ButtonV1, {ButtonV1Model, ButtonV1IsEmptyFn} from "@adobe/aem-core-components-angular-base/authoring/button/v1";

Using the imported code

Now that you have the Button and ButtonV1IsEmptyFn imported, you can use them in your project. The properties of the Button 1 on 1 correspond to the Sling Model Exporter (.model.json) output.

Note: There are some exceptions where some extra properties are added (mainly i18n labels) that are currently not present in the OOTB sling model exports. These can be added by the project itself with delegation. If they are not present, the default (English) values will be used.

Button - Example with the spa editor:

MapTo('my-project/wcm/components/button')(ButtonV1, {isEmpty: ButtonV1IsEmptyFn});

For a complete project with examples, visit the github page.