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

@tmplr/jest

v0.3.0

Published

Utilities for testing tmplr packages using jest

Downloads

3

Readme

@tmplr/jest

tests coverage version

Utilities for testing tmplr packages using jest.

npm i @tmplr/jest --save-dev

Usage

You need to have Jest installed and setup. Utilities provided by this package are only usable where Jest's globals are registered in the environment.

import { createTestSetup } from '@tmplr/jest'


test('stuff work ...', async () => {
  const { fs, log, scope, context, varcontext } = createTestSetup({
    files: {
      '/some/file.txt': 'its content',
      'relative.yml': 'some other content',
    },
    remotes: {
      'https://github.com/user/repo': {
        'README.md': 'some content',
        'other-file.js': 'console.log("HOLA!")',
      }
    },
    providers: {
      stuff: {
        thingy: async () => 'Ladida'
      }
    },
  })
 
  // 👉 write tests here ...
})

☝️ createTestSetup() function gets a test environment (with filesystem, available remotes, and data providers) and provides the basic primitives allowing you to create core tmplr constructs (such as runnables and executions) and test their behavior in the test environment you have created.

  • fs is a tmplr-compliance filesystem whose methods are also spiable Jest functions.
  • log is a change log recording all changes applied by executed runnables.
  • scope is the main execution scope, variables read by runnables will be available here, as will values provided via specified providers. Its methods are also spiable Jest functions.
  • context is an evaluation context (bound to scope) specifically for evaluating expressions within tmplr recipes.
  • varcontext is an external evaluation context, which is suitable for evaluating expressions in other files. In this context, only variables stored during execution are available (through a special namespace, which can be specified via varprefix option).

⚠️⚠️ WORK IN PROGRESS. DO NOT USE. ⚠️⚠️