JSPM

rollup-plugin-ts-paths

1.0.5
  • ESM via JSPM
  • ES Module Entrypoint
  • Export Map
  • Keywords
  • License
  • Repository URL
  • TypeScript Types
  • README
  • Created
  • Published
  • Downloads 648
  • Score
    100M100P100Q102365F
  • License MIT

Package Exports

  • rollup-plugin-ts-paths

This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (rollup-plugin-ts-paths) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.

Readme

rollup-plugin-ts-paths

Replace alias with resolved import from paths in tsconfig.json. Let's you use rollup to bundle/transpile code generated by tsc like this

// src/path/to/foo/foot.ts
import { Foo } from 'foo';

where foo is defined in tsconfig.json

{
  "compilerOptions": {
      "paths": {
        "foo": [
          "src/path/to/foo/foo.ts"
        ]
      }
  }
}

Installation

npm install --save-dev rollup-plugin-ts-paths

Usage

Generally, you need to ensure that rollup-plugin-ts-paths goes before other things (like rollup-plugin-commonjs) in your plugins array, so that the correc file can be resolved from an import.

// rollup.config.js
import tsConfigPaths from 'rollup-plugin-ts-paths';

export default {
  // ...
  plugins: [
    tsConfigPaths()
  ]
};

Options

{
  // The directory the TS config file can be found in (optional)
  tsConfigDirectory: processs.cwd()
}

Limitations

Currently on the first entry of a path specified in a tsconfig.json is supported.

License

MIT