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

lit-xml

v0.6.2

Published

Burning your XML documents to the ground? Yes please. In the mean time, let's use lit-xml.

Downloads

803

Readme

Lit XML 🔥

Burning your XML documents to the ground? Yes please. In the mean time, let's use lit-xml.

A small utility to help construction of XML documents using a simple tagged template. Because you sometimes have to use XML 🤷‍♀️.

🗺️ Installation

Install lit-xml locally within your project folder, like so:

npm i lit-xml

Or with yarn:

yarn add lit-xml

🎁 Usage

A simple example:

import { xml } from 'lit-xml';

const xmlFragment = xml`<foo bar="${41 + 1}">Some ${'<content>'}</foo>`.toString();
// => '<foo bar="42">Some &lt;content&gt;</foo>'

Importing xml will give you the default xml template literal. It will sanitize values, but not validate on well formed xml for performance reasons.

A more advanced scenario:

import { createLitXml } from 'lit-xml';
const xml = createLitXml({
  format: true,
  validators: [validators.isWellFormed],
  indent: 2,
});

xml`<foo bar="${41 + 1}"><baz></baz></foo>`.toString();
// => `<foo bar="42">
//       <baz/>
//     </foo>`

xml`<foo><foo>`.toString();
// InvalidXmlError! Error on line 1: Closing tag 'foo' is expected inplace of 'bar'.

const people = [{ name: 'foo' }, { name: 'bar' }];
xml`<people>${people.map((p) => xml`<person>${p.name}</person>`)}</people>`.toString();
// => `<people>
//      <person>foo</person>
//      <person>bar</person>
//    </people>`

In this example, the createLitXml factory method is used to create a custom xml template literal. In this case it will validate that the XML document is well-formed and it will be formatted (with an indent of 2 spaces).

🚀 Features

🧩 Construct xml documents using plain JS like conditional operators and Array.prototype.map
💄 vscode plugin for syntax highlighting
🚿 Interpolated values are sanitized
📐 Configurable well formed validation using fast-xml-parser
👓 Configurable formatting output using fast-xml-parser

💭 Motivation

JavaScript is not-XML friendly. We're missing good libraries to construct larger XML documents without relying on template libraries like ejs or handlebars.

This library is an attempt to solve this problem using the simple feature of tagged templates. It is inspired by the awesome lit-html.