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

@acoustic-content-sdk/tooling-contributions

v9.0.10076

Published

Tooling functions to implement support for feature modules.

Downloads

41

Readme

npm

Tooling functions to implement support for feature modules.

API Documentation

Home > @acoustic-content-sdk/tooling-contributions

tooling-contributions package

Tooling functions to implement support for feature modules.

Enumerations

| Enumeration | Description | | --- | --- | | ArtifactMode | Artifact modes, the values need to match the option selections for the Page Contribution type 354743b2-f89a-482b-b447-2b5a2367c8bd |

Functions

| Function | Description | | --- | --- | | createNgDriverArtifacts(aHost, aReadDir, aSchema) | Generates the content items that describe a driver based on an Angular build output | | createPackageArtifacts(aHost, aSchema, aLogSvc) | Generates the content items that describe a driver based on an Angular build output |

Interfaces

| Interface | Description | | --- | --- | | CreateNgDriverArtifactsSchema | | | CreatePackageFromArtifactsSchema | |

Variables

| Variable | Description | | --- | --- | | VERSION | Version and build number of the package |

Home > @acoustic-content-sdk/tooling-contributions > ArtifactMode

ArtifactMode enum

Artifact modes, the values need to match the option selections for the Page Contribution type 354743b2-f89a-482b-b447-2b5a2367c8bd

Signature:

export declare enum ArtifactMode 

Enumeration Members

| Member | Value | Description | | --- | --- | --- | | ALWAYS | "always" | | | LIVE | "live" | | | PREVIEW | "preview" | |

Home > @acoustic-content-sdk/tooling-contributions > createNgDriverArtifacts

createNgDriverArtifacts() function

Generates the content items that describe a driver based on an Angular build output

Signature:

export declare function createNgDriverArtifacts(aHost: ReadTextFile, aReadDir: ReadDirectory, aSchema?: CreateNgDriverArtifactsSchema): Observable<FileDescriptor<Artifact | Buffer>>;

Parameters

| Parameter | Type | Description | | --- | --- | --- | | aHost | ReadTextFile | callback to read a text file | | aReadDir | ReadDirectory | | | aSchema | CreateNgDriverArtifactsSchema | configuration |

Returns:

Observable<FileDescriptor<Artifact | Buffer>>

the sequence of artifacts

Home > @acoustic-content-sdk/tooling-contributions > createPackageArtifacts

createPackageArtifacts() function

Generates the content items that describe a driver based on an Angular build output

Signature:

export declare function createPackageArtifacts(aHost: ReadTextFile, aSchema?: CreatePackageFromArtifactsSchema, aLogSvc?: LoggerService): Observable<FileDescriptor<any>>;

Parameters

| Parameter | Type | Description | | --- | --- | --- | | aHost | ReadTextFile | callback to read a text file | | aSchema | CreatePackageFromArtifactsSchema | configuration | | aLogSvc | LoggerService | |

Returns:

Observable<FileDescriptor<any>>

the sequence of artifacts

Home > @acoustic-content-sdk/tooling-contributions > CreateNgDriverArtifactsSchema

CreateNgDriverArtifactsSchema interface

Signature:

export interface CreateNgDriverArtifactsSchema 

Properties

| Property | Type | Description | | --- | --- | --- | | configuration | string | The name of the configuration to use | | mode | string | mode | | project | string | The name of the project. | | tag | string | a comma separated list of tags |

Home > @acoustic-content-sdk/tooling-contributions > CreatePackageFromArtifactsSchema

CreatePackageFromArtifactsSchema interface

Signature:

export interface CreatePackageFromArtifactsSchema 

Properties

| Property | Type | Description | | --- | --- | --- | | data | string | Location of the data directory, defaults to 'data'. The package artifacts will be created in the parent folder of the data folder | | files$ | Observable<FileDescriptor<any>> | optionally the explicit list of files to include | | license | string | optinally the license, defaults to MIT | | tag | string | a comma separated list of tags |

Home > @acoustic-content-sdk/tooling-contributions > VERSION

VERSION variable

Version and build number of the package

Signature:

VERSION: {
    version: {
        major: string;
        minor: string;
        patch: string;
        branch: string;
    };
    build: Date;
}

Home > @acoustic-content-sdk/tooling-contributions > CreateNgDriverArtifactsSchema > configuration

CreateNgDriverArtifactsSchema.configuration property

The name of the configuration to use

Signature:

configuration?: string;

Home > @acoustic-content-sdk/tooling-contributions > CreateNgDriverArtifactsSchema > mode

CreateNgDriverArtifactsSchema.mode property

mode

Signature:

mode?: string;

Home > @acoustic-content-sdk/tooling-contributions > CreateNgDriverArtifactsSchema > project

CreateNgDriverArtifactsSchema.project property

The name of the project.

Signature:

project?: string;

Home > @acoustic-content-sdk/tooling-contributions > CreateNgDriverArtifactsSchema > tag

CreateNgDriverArtifactsSchema.tag property

a comma separated list of tags

Signature:

tag?: string;

Home > @acoustic-content-sdk/tooling-contributions > CreatePackageFromArtifactsSchema > data

CreatePackageFromArtifactsSchema.data property

Location of the data directory, defaults to 'data'. The package artifacts will be created in the parent folder of the data folder

Signature:

data?: string;

Home > @acoustic-content-sdk/tooling-contributions > CreatePackageFromArtifactsSchema > files$

CreatePackageFromArtifactsSchema.files$ property

optionally the explicit list of files to include

Signature:

files$?: Observable<FileDescriptor<any>>;

Home > @acoustic-content-sdk/tooling-contributions > CreatePackageFromArtifactsSchema > license

CreatePackageFromArtifactsSchema.license property

optinally the license, defaults to MIT

Signature:

license?: string;

Home > @acoustic-content-sdk/tooling-contributions > CreatePackageFromArtifactsSchema > tag

CreatePackageFromArtifactsSchema.tag property

a comma separated list of tags

Signature:

tag?: string;