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

jest-fixed-jsdom

v0.0.9

Published

A superset of the JSDOM environment for Jest that respects Node.js globals.

Downloads

473,151

Readme

[!WARNING] This package is never meant as a solution to anything. This is a workaround. Please consider testing browser code in the actual browser. You can do so both in Vitest and in Playwright at the moment.

Motivation

When you use Jest with JSDOM you are getting a broken test environment. Some Node.js globals cease to exist (e.g. Request, Response, TextEncoder, TextDecoder, ReadableStream1), while others stop behaving correctly (e.g. Event, MessageEvent2, structuredClone()3). That is caused by jest-environment-jsdom and JSDOM relying on polyfills to implement standard APIs that have been available globally both in the browser and in Node.js for years.

Here's a piece of valid JavaScript that works in both the browser and Node.js but fails in Jest/JSDOM:

new TextEncoder().encode('hello')
ReferenceError: TextEncoder is not defined

We strongly believe that a valid JavaScript code must compile regardless of what test environment you are using. In fact, having a proper test environment is crucial to get any kind of value from your tests. Jest/JSDOM take that already working environment away from you.

We've built this project aims to fix that problem, restoring the global APIs that are present in both environments, providing better interoperability, stability, and consistent runtime behavior.

Changes

This project "fixes" the following global APIs, overriding whichever polyfills they have with respective Node.js globals:

  • fetch()
  • Blob
  • FormData
  • Headers
  • Request
  • Response
  • ReadableStream
  • TextEncoder
  • TextDecoder
  • TextEncoderStream
  • TextDecoderStream
  • structuredClone()
  • URL
  • URLSearchParams
  • BroadcastChannel
  • TransformStream

Getting started

Install

npm i jest-fixed-jsdom --save-dev

Configure Jest

In your jest.config.js, set the testEnvironment option to jest-fixed-jsdom:

// jest.config.js
module.exports = {
  testEnvironment: 'jest-fixed-jsdom',
}

You can use any other testEnvironmentOptions you need. Those will be forwarded to the underlying jest-environment-jsdom.