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

@netvlies/wsc-js-moduleloader

v2.0.0

Published

module loader to be imported in skeletons

Downloads

39

Readme

wsc-moduleloader

The purpose of this module is to abstract the module loader and base module components so they can be implemented independently.

Setup

The module can be installed by running:

npm i -D @netvlies/wsc-js-moduleloader

Usage

Create modules in your HTML using the module selector (default: [data-module="Name"]).

<nav data-module="Navigation">
    <ul>...</ul>
</nav>

Initialize the module loader in your source code using this setup:

import ModuleLoader from '@netvlies/wsc-js-moduleloader';

import Navigation from './modules/Navigation';

const moduleLoader = new ModuleLoader({
    Navigation
});

Create the modules using the default framework in the Base module.

Module initialization priority

Starting at v1.1.0, you may use the new attribute data-module-priority to decide on the initialization priority of modules. By default all modules are executed on an idle callback. This means the default behavior is initializing modules when the browser is idle. Sometimes you may need to give priority initialization to a module. For example, because it is the first thing that's visible in a users window, like the Navigation example. You can bypass the idle callback by setting the data-module-priority attribute to instant:

<nav data-module="Navigation" data-module-priority="instant">
    <ul>...</ul>
</nav>

Instant means: do not wait for an idle moment and initialize this module instantly, asap.