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 🙏

© 2025 – Pkg Stats / Ryan Hefner

mass-htl

v0.1.4

Published

A wrapper npm module using @adobe/htlengine to parse multiple HTL files from a directory and copy the results to a target directory

Readme

A wrapper npm module using @adobe/htlengine to parse multiple HTL files from a directory and copy the results to a target directory

npm install mass-htl Usage: node mass-htl Will compile all .html files inside source dir and subdirectories and put the results in target dir using the same structure from the source dir path.

Example: node compile.js src compiled

  • myproject
    • src
      • banana
        • htlmock
        • banana.html
      • apple.html
    • compile.js Will result in:
  • myproject
    • src
    • compiled
      • banana
        • banana.html
      • apple.html
    • compile.js

Sling models used throught data-sly-use will need to be in the a /htlmock subdirectory of the .html file. Example: Directory

  • myproject
    • src
      • htlmock
        • code.banana.BananaSlingModel.js
      • banana.html
    • compile.js Contents of banana.html:

Contents of code.banana.BananaSlingModel.js: module.exports = class MyUseClass { use() { console.log(global.process.argv); return { title: 'Banana' }; } };

run the following command from the /myproject directory: node mass-htl src compiled.

After compilation the following file will appear: /myproject/compiled/banana.html It will contain:

Mocking global objects/data: When you create a file called mock.json inside your /htlmock folders, mass-htl will read the json contents of the file and add the objects to the global scope when compiling the htl files. Example contents of mock.json: { "properties": { "jcr:title": "My page title" } } You can also use the contents of this file to point data-sly-resource nodes that utilize resourceType to the supplied file Example: { "apps/myapp/components/title": "mocktitle.html" } The above will result in all nodes that containe data-sly-resource="@resourceType=/apps/myapp/components/title" to point to "mocktitle.html" instead.

Note: If you want to be able to use data-sly-include, you will have to target either the jcr_root/apps/ aem folder or the same folder as the component. You can only use data-sly-include on components that exist in the same module.