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

unplugin-resolve-esm-ts-paths

v0.1.1

Published

Resolve `import` and `export` expressions using the TSConfig `paths` and `baseUrl`. This was made to be used on Node environments where you need to have relative imports and most transpile tools (even `tsc` itself) doesn't change imports.

Downloads

110

Readme

unplugin-resolve-esm-ts-paths

Resolve import and export expressions using the TSConfig paths and baseUrl. This was made to be used on Node environments where you need to have relative imports and most transpile tools (even tsc itself) doesn't change imports.

Powered by get-tsconfig and es-module-lexer.

Features

  • Resolve TSConfig paths to relative paths.
  • Add index files for directory imports.
  • Add file extensions.
  • Extra: Ability to have glob imports. Import paths containing the glob: keyword will be parsed by the plugin and the default imports of every file matching the glob will be added to the file. The result will be a variable containing an array with all the default exports.

With this TSConfig and Options:

{
  "baseUrl": "src",
  "paths": {
    "@test/*": [
      "test/*"
    ],
  },
}
{
  ext: '.ts',
  resolveGlob: true,
  resolvedExt: '.js',
}

In:

import foo from './foo'
import doubleQ from "./doubleQ"
import { build } from 'esbuild'
import item from '@test/file'
import glob from 'glob:./*.js'

Out:

import foo from './foo.js'
import doubleQ from './doubleQ.js'
import { build } from 'esbuild'
import item from './src/test/file.js'
import module0 from './randomModule.js'
import module1 from './anotherRandomModule.js'
import module2 from './yetAnotherRandomModule.js'
const glob = [module0, module1, module2]

Options

  • ext (default: .ts): Which file extension should the plugin match.
  • resolvedExt (default: .js): Which extension should be added to the imports.
  • resolveGlob (default: false): If glob expressions should be resolved.

Usage

// vite.config.ts
import unpluginResolveEsmTSPaths from 'unplugin-resolve-esm-ts-paths/vite'

export default defineConfig({
  plugins: [
    unpluginResolveEsmTSPaths({ /* options */ }),
  ],
})
// rollup.config.js
import unpluginResolveEsmTSPaths from 'unplugin-resolve-esm-ts-paths/rollup'

export default {
  plugins: [
    unpluginResolveEsmTSPaths({ /* options */ }),
    // other plugins
  ],
}

// webpack.config.js
module.exports = {
  /* ... */
  plugins: [
    require('unplugin-resolve-esm-ts-paths/webpack')({ /* options */ }),
  ],
}

// esbuild.config.js
import unpluginResolveEsmTSPaths from 'unplugin-resolve-esm-ts-paths/esbuild'

build({
  /* ... */
  plugins: [
    unpluginResolveEsmTSPaths({ /* options */ }),
  ],
})

Types

If you want to solve the ts(2307) issue for the glob imports, you can add this to one of your .d.ts type definitions:

declare module 'glob:*' {
  const modules: unknown[];
  export default modules;
}