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

@netcentric/component-loader

v1.0.2

Published

Load components for plain javascript projects

Downloads

2,232

Readme

@netcentric/component-loader

Description

Version Build Status CodeQL Analysis semver: semantic-release License

Installation

npm install @netcentric/component-loader

important!

This module is not transpiled. If your project is excluding node_modules you will have to update regex to include this module.

Eg:

// webpack babel-loader config
module.exports = {
  exclude: /node_modules\/(?!@netcentric)/,
  loader: 'babel-loader',
  ...
};

Here we are excluding node_modules, except the ones under node_modules/@netcentric/*

Usage

  1. Register component:
register({ componentName: ComponentClass });
  1. Initialize component
runComponent('componentName');

or initialize all components

run();
  1. Bind component to DOM
<div data-nc="componentName"
     data-nc-params-componentName="{}"></div>

Example

in the component file you should register your component

import { register } from '@netcentric/component-loader';

class Text {
  ...
}
// register your component to be loaded
register({ Text });

At your main entry file you should run all registered components

import {
  observe,
  run
} from '@netcentric/component-loader';

// Run all registered component
run();
// Optional: Use observe to initialize new components which  are added to the DOM after initial run.
observe();

API and examples

This version uses standalone functions to allow tree shaking and to only use necessary parts.

adding it to HTML

Adding one component

<div data-nc="Component1"
     data-nc-params-Component1="{}"></div>

Adding more than one component

<div data-nc="Component1,Component2"
     data-nc-params-Component1="{}"
     data-nc-params-Component2="{}"></div>

register

This method will register components constructor in loaderComponents You can register individual component, or list

Parameters

/**
 * Constant with a object that contain collection of components classes.
 * 
 * @param {object} newComponents - Components collection { name: definition }
 * @param {number} [level] - level of inheritance
 */
  const register = (newComponents, level) => {}

Examples


import { register } from '@netcentric/component-loader';
import { title } from 'components/title';
import { text } from 'components/text';

// Add 2 components named title, and text
register({ title, text });

Or you can register several components based on proper named exports


import { register } from '@netcentric/component-loader';
import * as components from 'components';

// register all components exported as proper named exports on components/index.js

register({ components });

Level is used in multilevel inheritance, eg if you have one base project with component HTML, and want to override just JS part in sub project

  1. Base project
import { register } from '@netcentric/component-loader';

class Title {
  init() {
    console.log('level 0 Title');
  }
}

register({ Title }, 0);
  1. Sub project
import { register, components } from '@netcentric/component-loader';

class Title extends components[0].Title {
  init() {
    console.log('level 1 Title');
  }
}

register({ Title }, 1);

run

This will run the loader on previously registered components.

Parameters

/**
 *  Run the loader on a element to get all attributes that corresponds to a component
 *  @param {HTMLElement} [element] root element
 *  @param {string} [initAttr] attribut name
 */
  const run = (element = window.document, initAttr = 'data-nc') => {}

Examples


import {
  register,
  run
} from '@netcentric/component-loader';

// eg components
import { title } from 'components/title';
import { text } from 'components/text';

// Add 2 components named title, and text
register({ title, text });
// then you run so it will create if any HTMLelement with a default attribute have any component to start
run();

// Or load components only on a specific element and search a different attribute like `data-components`
const main = document.querySelector('main');
run(main, 'data-components');

components

Here is just a constant to store the available constructors (functions or classes) of components. We store it on its own file so it can be imported into separated files and without having to import the other components logic.

If you want to access all components constructors you can just import it in any file like:


import { components } from '@netcentric/component-loader';

instances

This object will store all instances of components separated by [className][instanceId]. We store it on its own file, so it can be imported into separated files and without having to import the other components logic.

If you want to access all the instances of components you can just import it in any file like:


import { instances } from '@netcentric/component-loader';

const howManyTitles = instances.title.length;

// eg of querying title components by uuid
const getTitleByUUID = (uuid) => instances.title.filter(instance => instance.el.uuid === uuid);
const mytitle = getTitleByUUID('a8c405b5-1928-46ed-afa1-5a0a3f4dde6c');