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

ts-jest-resolver

v2.0.1

Published

A resolver for `jest` that uses same strategy as TS when resolving files with JavaScript extension (".js").

Downloads

131,549

Readme

ts-jest-resolver

Build Status License

A resolver for jest that uses the same strategy as TS when resolving files with JavaScript extensions (".js", ".jsx", ".cjs" and ".mjs"). It works pretty well with ts-jest or babel with @babel/preset-typescript.

  • 📦 Distributions in ESM and CommonJS.
    • Supports both Node.js ESM (import/export) and CommonJS (require/module.exports).
  • ⚡ Lightweight:
    • It's bundled using rollup.js.
  • 🔋 Bateries included:
    • It just depends on jest-resolver types.
  • ✅ Safe:

Usage

This library is published in the NPM registry and can be installed using any compatible package manager.

npm install ts-jest-resolver --save

# For Yarn, use the command below.
yarn add ts-jest-resolver

After installation, you can set "ts-jest-resolver" as jest's resolver.

// jest.config.js

module.exports = {
  preset: "ts-jest",
  resolver: "ts-jest-resolver",
};

How it works

It changes module's extension to resolve in the same way as TypeScript.

How it works with ".js" and ".jsx" extensions

When importing from path with JavaScript extension (".js" or ".jsx"):

import EventEmitter from './EventEmitter.js';
  1. It tries to resolve to a path with ".tsx";

    import EventEmitter from './EventEmitter.tsx';
  2. If no file was found, it tries to resolve to a path with ".ts";

    import EventEmitter from './EventEmitter.ts';
  3. If no file was found, it resolves to original path (with ".js" or ".jsx").

    import EventEmitter from './EventEmitter.js';

How it works with ".mjs" and ".cjs" extensions

When importing from path with ES or CommonJS modules (".mjs" and ".cjs" respectively):

Ex.

import parse, { Tokenizer } from './parser.mjs'
import { discoverPath } from './getFiles.cjs';
  1. It tries to resolve to paths with ".mts" and ".cts".

    Ex.

    import parse, { Tokenizer } from './parser.mts'
    import { discoverPath } from './getFiles.cts';
  2. If no files were found, it resolves to original paths (with ".mjs" and ".cjs").

    Ex.

    import parse, { Tokenizer } from './parser.mjs'
    import { discoverPath } from './getFiles.cjs';

License

Released under MIT License.