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

@api-components/api-console-dependency-manager

v1.0.4

Published

Module to detect and install Mulesoft's API console dependencies.

Downloads

73

Readme

api-console-dependency-manager

Build Status

A npm module to detect and install Mulesoft's API console dependencies.

This module is mainly used in the api-console-builder.

API

Shorthand functions:

  • installDependencies(workingDir, logger, opts) -> new DependendenciesManager#installDependencies(workingDir, logger, opts)

The module exposes 2 classes:

Example

const consoleDependencies = require('api-console-dependency-manager');

consoleDependencies.installDependencies('./build/', console, {
  verbose: true,
  parser: true,
  app: true
})
.then(() => console.log('Dependencies are now installed'))
.catch(cause => console.error(cause));

equivalent to

const {DependendenciesManager, DependenciesOptions} = require('api-console-github-resolver');

const options = new DependenciesOptions({
  verbose: true,
  parser: true,
  app: true
});
const workingDir = './build/';
const logger = console; // Winston or other with console like interface
const manager = new DependendenciesManager(workingDir, logger, options);
manager.installDependencies()
.then(() => console.log('Dependencies are now installed'))
.catch(cause => console.error(cause));

DependenciesOptions

| Property | Type | Default | Description | | -------- | -------- | -------- | -------- | | verbose | Boolean | false | Prints verbose output while installing dependencies. This is used to build install command for bower which is printing console output by default. | | parser | Boolean | false | If set it installs RAML javascript parser with the enhancer. Deprecated: This option is only relevant for the console version 4. It may be removed in future releases. Set isV4 option when using this one. | | app | Boolean | false | If set it installs app-route element to support standalone application architecture of the API console. Deprecated: This option is only relevant for the console version 4. It may be removed in future releases. Set isV4 option when using this one. | | isV4 | Boolean | false | Compatibility mode with API console version 4. If set then it works as module created for v4 (versions 0.x.x of the module) | | optionalDependencies | Array<String> | undefined | List of optional dependencies to install besides the ones installed with bower file. It contains the list to of bower dependencies as it would be defined in bower.json file. This isn relevant for console v5 build process which manages dependencies differently. |

DependendenciesManager

Constructor

Arguments

| Property | Type | Description | | -------- | -------- | -------- | | workingDir | String | Path to a working directory where the console is processed. Usually it's where the bower.json file is. | | options | Object or DependenciesOptions | Build options passed to the module. | | logger | Object | Any logger with the interface compatible with platform's console object. |

installDependencies()

Installs dependencies in the workingDir.

Return

Resolved promise when operation is completed.

Changes in stable version

  • Order of arguments is reversed
  • It uses locally installed Bower dependency and does not checks if bower is installed on local machine.
  • Now additional dependencies has to be defined in the configuration options