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

tsc-alias-2

v1.0.3

Published

Alias tsc's output, including file extensions and node_modules aliasing! You can run your code directly in node or the browser with NO BUNDLING!

Downloads

2

Readme

tsc-alias-2

Alias tsc's (typescript's) output, including file extensions and node_modules aliasing! You can run your code directly in node or the browser with NO BUNDLING! Each output file maps exactly to one source file.

Example here

How

npm i -g tsc-alias-2 # or
npm i --save-dev tsc-alias-2

You probably want outDir and rootDir in your tsconfig.json:

{
    "compilerOptions": {
        "outDir": "./dist/",
        "rootDir": "./src/"
    }
}

Then just run tsc && tsc-alias-2 instead of your build step. It will map paths specified in the tsconfig as well.

Using the result

For the browser, put this in your index.html:

<script type="module">
    import { whatever } from './dist/index.mjs'
    alert(whatever())
</script>

For node, it's just a

node ./dist/index.mjs

Why

Chrome performance profiling doesn't work very well with a bundle + sourcemap. It works much better with separate source files. I needed detailed perf on some code, so I made this.

  • tsc-alias doesn't point to node_modules paths so you can't run in the browser at all! Node doesn't work either because the extensions were wrong. So tsc-alias-2 also renames *.js to *.mjs so node expects it to be a module.
  • digital-loukoum/tsc-esm seemed to have some bugs. This is largely based on it.

Library

You can also use import it if you have a js build script or something:

const tscAlias2 = require('tsc-alias-2')
// Checks the tsconfig and does subs:
tscAlias2.main()
// Pass in args directly instead:
tscAlias2.replaceAllImports('./dist/', [{ pattern: '@/*', replacement: './' }])