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 🙏

© 2026 – Pkg Stats / Ryan Hefner

@stzhu/metro-ts-resolver

v0.1.3

Published

A custom Metro resolver that enables `.js` extensions for TypeScript imports

Readme

@stzhu/metro-ts-resolver

A custom Metro resolver that enables .js extensions for TypeScript imports in React Native projects.

The Problem

TypeScript allows the use .js extensions in import statements, while the actual files are .ts or .tsx:

// The file is actually Button.tsx, but you import it as .js
import { Button } from './Button.js';

Metro's default resolver doesn't support this pattern and tries to resolve to the .js file. If you choose to use .js extensions in your TypeScript imports, Metro fails to resolve them to the actual .ts/.tsx files, causing resolution errors.

This package adds support for this pattern by using TypeScript's own module resolution to correctly map .js imports to their corresponding TypeScript files.

Installation

pnpm add -D @stzhu/metro-ts-resolver

Usage

Update your metro.config.js to use the custom resolver:

const { createTsResolveRequest } = require('@stzhu/metro-ts-resolver');

const config = {
  /// ...
};

module.exports = {
  ...config,
  resolver: {
    ...config.resolver,
    resolveRequest: createTsResolveRequest({
      projectDir: __dirname,
      // Optional: specify a custom tsconfig filename
      // tsconfigName: 'tsconfig.json'
    }),
  },
};

That's it! Now you can use ESM-style imports in your TypeScript files:

// App.tsx
import { Button } from './components/Button.js'; // ✅ Works!
// or
import { Button } from '@workspace/ui/Button.js'; // ✅ Works!

How It Works

When Metro encounters a .js import from a TypeScript file, this resolver:

  1. Uses TypeScript's module resolution to find the actual file (.ts, .tsx, etc.)
  2. Resolves the import with the correct extension
  3. Falls back to Metro's default resolution for all other cases

The resolver respects your tsconfig.json configuration, including paths, baseUrl, and other module resolution settings.

Requirements

  • Metro >= 0.83.0
  • TypeScript 5.x

References