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

@web-component-wrapper/angular

v0.4.5

Published

> [!WARNING] > CAUTION: This package is currently in the early stages of development, and its API may undergo changes in the future.

Downloads

3

Readme

@web-component-wrapper/angular

[!WARNING] CAUTION: This package is currently in the early stages of development, and its API may undergo changes in the future.

Create Angular components from a web component library.

Specification

#1 Angular Directive

Each component is designated as an Angular directive instead of a component, eliminating unnecessary wrapper elements. This ensures transparency to the web component library, as it does not need to be aware of any wrappers.

#2 Angular Standalone Component

Each component is defined as a standalone Angular component, enabling you to import them into NgModule or other standalone components.

#3 Each component with separate ng-packagr entry

Each component establishes its own entry point for ng-packagr, eliminating the need to re-export them in the library's public API. This prevents the library's public API from being polluted with types, events, and interfaces from all components and avoids naming collisions.

import { TagLitTs, TagRemoveEvent, TagSize } from 'library-angular-components/components/tag-lit-ts';

Supported features

  • [X] Description
  • [X] Properties/Inputs
  • [X] Events/Outputs
  • [X] Slots (via docs)
  • [X] Css custom properties (via docs)
  • [ ] Methods

Installation

npm i @web-component-wrapper/angular -D

Configuration

interface AngularComponentsOptions {}

Usage

const { processProject } = require('@web-component-wrapper/core');
const { AngularComponentsGenerator } = require('@web-component-wrapper/angular');

processProject({
  ...,
  generator: new AngularComponentsGenerator({
    /// ... and/or other options from AngularComponentsOptions
  })
});

Example

👀 library-angular-components is an example Angular library that generates Angular component for components-library