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-console-lwc

v0.1.7

Published

API Console LWC

Downloads

6

Readme

API Console LWC

API Documentation tool built using LWC.

Getting started

npm install @mulesoft/api-console-lwc

We ship our components ready for both platform and non-platform usage. Below you can find guides to using the components in each scenario.

Salesforce DX project

You can find the Salesforce-ready components under the node_modules/@mulesoft/api-console-lwc/dist/arc folder.

We recommend the following to take into consideration:

  • Ignore test files
  • Add the appropriate -meta.xml files for your project's use case
  • Import the markdown component manually*

*This component should be imported manually because the markdown component imports a library (showdown), which needs to be loaded before rendering.

Regular Node usage

You should be able to import the bundle script with

import '@mulesoft/api-console-lwc`

Running this script will register the components to the browser's registry, and allow you to to render them like normal web components in your project.

Contributing

Take a look at our Contributing Guidelines.

How to start?

Start simple by running npm start. This will start the project with a local development server.

The source files are located in the src folder. All web components are within the src/arc folder. The folder hierarchy also represents the naming structure of the web components. The files for running the local demo can be found in the src/demo folder.