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

xtypejs-extension-typename-utils

v0.1.1

Published

xtypejs Extension - Type Name Utilities

Downloads

5

Readme

xtypejs Extension - Type Name Utilities

This extension provides the xtypejs type name utility API methods, which provides a way to enumerate all available types in xtypejs either by name or by id, and to convert between them.

The methods provided are:

  • xtype.util.nameToId
  • xtype.util.idToName
  • xtype.util.typeNames
  • xtype.util.typeIds

Installation with npm

npm install xtypejs-extension-typename-utils --save

NodeJs import and setup

var xtype = require('xtypejs');
var xtypejsTypeNameUtilsExtension = require('xtypejs-extension-typename-utils');

// The type name utility methods are NOT available here

xtype.ext.registerExtension(xtypejsTypeNameUtilsExtension);

// The type name utility methods are now available here

HTML script tag import and setup

Include the extension script after the xtypejs script to automatically register the extension into xtypejs without exporting any globals. This relies on xtypejs being available in the xtype global variable.

<script src="path/to/xtype.js"></script>
<script src="path/to/xtypejs-extension-typename-utils.js"></script>

<script>
    // The type name utility methods are available here
</script>

If the extension script needs to be included before the xtypejs script, or the xtype global is not available (or is using a different variable name) when the extension script is included, the extension will be exported instead to a global variable named xtypejsTypeNameUtilsExtension, which must then be manually registered into xtypejs as an extension.

<!--
    Assume 'xtype' global variable not available here. The following
    exports global variable 'xtypejsTypeNameUtilsExtension'
-->
<script src="path/to/xtypejs-extension-typename-utils.js"></script>

<!-- Other things here... -->

<script>
    // Assume xtypejs later available here in variable 'myXtype'
    myXtype.ext.registerExtension(xtypejsTypeNameUtilsExtension);

    // The type name utility methods are now available here
</script>

Usage

For usage, see:

  • xtype.util.nameToId - doc
  • xtype.util.idToName - doc
  • xtype.util.typeNames - doc
  • xtype.util.typeIds - doc

Preventing name collisions

If the HTML script tag was used to import the extension script in a browser environment and in the absence of xtypejs in the xtype global variable, the extension will be exported to a global variable named xtypejsTypeNameUtilsExtension. The noConflict method of the exported extension can be used to reassign the extension to a different namespace or variable name, and return the global xtypejsTypeNameUtilsExtension variable to its previous value prior to including the extension script.

var myExtension = xtypejsTypeNameUtilsExtension.noConflict();

/*
 * myExtension is now xtypejsTypeNameUtilsExtension, while 
 * xtypejsTypeNameUtilsExtension variable is now returned to
 * its original value prior to inclusion of the extension script.
 */