JSPM

vue-cli-plugin-ts-paths

0.0.4
  • ESM via JSPM
  • ES Module Entrypoint
  • Export Map
  • Keywords
  • License
  • Repository URL
  • TypeScript Types
  • README
  • Created
  • Published
  • Downloads 136
  • Score
    100M100P100Q68685F
  • License MIT

Configure path aliases only once and in the right place (tsconfig.json)

Package Exports

  • vue-cli-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 (vue-cli-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

🚑 vue-cli-plugin-ts-paths

DRY, configure path aliases only once and in the right place.

Never heard of path aliases? One of many articles on how it makes our life easier https://netbasal.com/sexier-imports-in-typescript-e3c645bdd3c6

Use case

You are tired of duplicating code when you need to add a new path alias (alias section in webpack config and paths section in tsconfig.json).

Now you can add it only to tsconfig.json and no longer worry about the rest

Getting Started

A new project

If yon don't have a project, you can create TypeScript project using vue cli:

vue create my-vue-lib

Or use preset vatson/vue-ts-lib that includes ts-paths and ts-bundler plugins to speed up the development of any components library More information you can find here https://github.com/vatson/vue-ts-lib

Adding to a project

Install the plugin into your project:

cd my-vue-app
vue add ts-paths

That's it. You do not have to do anything else. Just add new aliases to tsconfig.json.

License

MIT