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

babel-plugin-test-export

v1.0.0

Published

Export private variables and functions to your tests

Downloads

48

Readme

babel-plugin-test-export

Build Status

Export private variables and functions to your tests. Annotate variable and function declarations with a // @test-export comment and they will be exported in a __test__ property of the module. Use values exported like this to write more focused tests or to mock things.

Install

$ yarn add --dev babel-plugin-test-export

Make sure to add this plugin only for tests. Example, in your .babelrc:

{
  // ... your common configuration ...
  env: {
    test: {
      plugins: [ "test-export" ]
    }
  }
}

Example

mylib.js:

// @test-export
function appendFoo(str) {
    return str + "foo"
}

module.exports = function (str) {
    return appendFoo(str).toUpperCase()
}

mylibSpec.js (jasmine example):

const mylib = require("./mylib")

// Test private functions!
describe("appendFoo", () => {
    const { appendFoo } = mylib.__test__
    it("appends foo", () => {
        expect(appendFoo("a")).toBe("afoo")
    })
})

// Mock private functions!
describe("mylib", () => {
    it("appends foo and turn value in uppercase", () => {
        spyOn(mylib.__test__, "appendFoo")
        expect(mylib("a")).toBe("AFOO")
        expect(mylib.__test__.appendFoo).toHaveBeenCalled()
    })
})

How it works

All references of the annotated variables and functions are rewritten to use the exported reference instead. The above example is rewritten as:

const __test__ = {};

// @test-export
__test__.appendFoo = function appendFoo(str) {
    return str + "foo";
};

module.exports = function (str) {
    return (void 0, __test__.appendFoo)(str).toUpperCase();
};
module.exports.__test__ = __test__

Drawbacks

  • Currently, it only works with commonjs exported modules.
  • Function and variable declarations are not hoisted anymore, so make sure to always write declarations before using them.

Inspiration and thanks

I used babel-strip-test-code as a start to write this plugin. Its goal is quite similar: export private values via a export __test__ = { ... } and it will strip this export for you in production. This approach, while quite simpler than mine, is a bit more verbose and doesn't allow mocks.