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

@adessa-node/worlds

v0.4.6

Published

1. [Why](#why) 1. [Commands](#Commands) 1. [How use](#how-use)

Downloads

12

Readme

Worlds App

  1. Why
  2. Commands
  3. How use

Why

Worlds app is a librery oriented to show a catalog of products in the shape of a carousel

Commands

  • make init: It will download the project's dependencies and configure git hooks.
  • npm run start: It will start a server on http://localhost:9000 with the code.
  • npm run dev: It will start compiling the code on dev mode and it will be looking for new changes.
  • npm run lint: It will run the lint rules on the project.
  • npm run test: It will run the unit tests + it's going to show the current code coverage of the project.
  • make build: It will create the build meant for production ready lib.

How use

To use this project, the following are required:

DEV:

<!-- ... -->
<head>
  <!-- ... -->
  <script>
    var configuration = {...}
  </script>
  <script src="path/of/statics/js/app.js" defer></script>
</head>
<body>
  <!-- ... -->
  <section id="app"></section>
  <!-- ... -->
</body>
<!-- ... -->

PROD:

<Worlds configuration={configuration} />;

The configuration should be as follows:

  • id <string>: id of configuration. default ''
  • name <string>: name of configuration. default ''
  • zoneKey <string>: zoneKey of configuration. default ''
  • cartridgeId <string>: identifier for endeca. default ''
  • dynamicData <object>: data configured in endeca
    • endPoint <string>: endpoint for get information of world by id.
    • worlds <arrayOf(<object>)>: array of world object.
      • id <string>: id of world
      • name <string>: name of world
      • activeIconUrl <string>: url of active icon
      • passiveIconUrl <string>: url of deactive icon
      • mDetailDebugInfo <bool>: debugger mod. default false
      • mComponentFieldDataConfigDomId <string>:
      • mTrackDTODetail <bool>: track dto detail. default true
  • rawZoneKey <string>: name of the zone
  • type <string>: type of component. dafault html
  • key <string>: key for find in endeca