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

node-resolve-ts

v1.0.2

Published

NodeJS hook to resolve `.ts` files when a `.js` file is imported so that --experimental-strip-types works

Downloads

17

Readme

Node Resolve TypeScript

Overview

Actually use node --experimental-strip-types to run regular Typescript code by allowing Node to resolve .ts files when it finds a .js import extension.

ESM (and therefore Node running ESM) needs the full file extension to resolve relative imports to source files. Since one of Typescript's fundamental philosophies is to never transform an existing valid JS construct into something else, it also needs the full extension of the output file when using the strict module resolution algorithm, meaning Typescript expects .js extensions in imports even when referencing a relative .ts source file. Since Node's type striping does nothing to help Node resolve a .ts file for a .js import specifier, Node will error as soon as it encounters a Typescript ESM import of another Typescript file.

Example

cat << EOF > add.ts
export function add(a: number, b: number): number {
  return a + b;
}
EOF

cat << EOF > main.ts
import { add } from './add.js';

console.log(add(2,3));
EOF

node --experimental-strip-types main.ts

# Results in:

# node:internal/modules/esm/resolve:257
#    throw new ERR_MODULE_NOT_FOUND(
#          ^
#Error [ERR_MODULE_NOT_FOUND]: Cannot find module '/home/example/add.js' imported from /home/example/main.ts

node --experimental-strip-types --import node-resolve-ts/register main.ts

# Results in: 5

Installation

To install this module locally in your project:

npm install node-resolve-ts

Or use your package manager of choice.

Usage

Import the registration module before your Typescript code loads. Node will now prefer to load .ts files if they exist but fall back to the .js otherwise.

node --experimental-strip-types --import node-resolve-ts/register main.ts

If you would rather load the .js file preferentially over the .ts when both exist, use this:

node --experimental-strip-types --import node-resolve-ts/register-prefer-js main.ts

Alternative Usage

If you can't use the above method, an alternative is to import node-resolve-ts/register in your entry file and then dynamically import the rest of your code. Since the static import runs first, the resolve hook will be installed and ready by the time the dynamic import run.

// entry.ts
import "node-resolve-ts/register";
import("./main.js");

// main.ts
import { here } from './a-typescript-file.js';
the.rest(of: your): code {
  here();
}
# Then run your entry.ts with regular type stripping
node --experimental-strip-types entry.ts