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

xml-templater-loader

v2.0.2

Published

webpack loader which replaces tags in html document with predefined tags

Downloads

2

Readme

xm-templater-loader

xml-templater-loader is a loader for webpack.

The main goal is to reuse html components:

For example, if you have something like a StringField.

#!html

<div class="string-field">
<label for="string-field-1">Name:</label>
<input type="text" id="string-field-1" />
</div>

Requirements are, that the structure of this string field (the above html) is always the same. Only the data changes. If you have, say 100 StringFields on your page, you have 100x times this html.

The disadvantages are clear:

  • If you change the html of a StringField (lets say, you want to add the property enabled), you need to modify everywhere, where you use it.
  • You html documents are more difficult to maintain, because is easier to read than ...

The xml-templater solves this problem by providing templates. You can define components. Components are just some html, with additonal parameters.

File StringField.html

#!html
<div class="string-field">
   <label for="string-field-1">Name:</label>
   <input type="text" id="string-field-1" name="{{name}}" />
</div>

In the component definition, you can use the Mustache templating language.

Children are always passed as an string array with the variable "children".

xml-templater will now transform any given document which consists basically out of xml to html.

#!xml

<!DOCTYPE html>
<html>
<body>
<StringField name="form1-name" />
</body>
</html>

will be transformed into:

#!html

<!DOCTYPE html>
<html>
<body>
<div class="string-field">
   <label for="string-field-1">Name:</label>
   <input type="text" id="string-field-1" name="form1-name" />
</div>
</body>
</html>

This reduces redundancy in html documents and make it easier to change each component like a StringField

Limitations

  • xml-templater-loader cannot handle the string `` or any other DOCTYPe at the beginning of the document.
  • the file to transform needs to have a root element.