JSPM

  • ESM via JSPM
  • ES Module Entrypoint
  • Export Map
  • Keywords
  • License
  • Repository URL
  • TypeScript Types
  • README
  • Created
  • Published
  • Downloads 1043
  • Score
    100M100P100Q83545F
  • License ISC

Advanced log generator for log engine

Package Exports

  • vite-tsconfig-log
  • vite-tsconfig-log/index.js

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 (vite-tsconfig-log) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.

Readme

vite-tsconfig-log

npm version

A Vite plugin that logs your tsconfig.json paths and aliases configuration during development.

Features

  • Displays resolved TypeScript paths and aliases in the console
  • Helps debug TypeScript path configuration issues
  • Lightweight with zero dependencies
  • TypeScript support included

Installation

Install with npm:

npm install vite-tsconfig-log --save-dev

Or with yarn:

yarn add vite-tsconfig-log -D

Usage

Add the plugin to your vite.config.ts:

import { defineConfig } from 'vite'
import tsconfigLog from 'vite-tsconfig-log'

export default defineConfig({
  plugins: [
    tsconfigLog()
  ]
})

When you run your Vite dev server, you'll see your tsconfig paths and aliases logged to the console.

Configuration Options

The plugin accepts the following options:

tsconfigLog({
  logLevel?: 'info' | 'warn' | 'error' | 'silent', // default: 'info'
  showAliases?: boolean, // default: true
  showPaths?: boolean, // default: true
  tsconfigPath?: string // default: './tsconfig.json'
})

Example Output

[vite-tsconfig-log] TSConfig Paths Configuration:
  @/* => src/*
  components/* => src/components/*

[vite-tsconfig-log] Resolved Aliases:
  @ => /project/src
  @components => /project/src/components

License

MIT © [Mike Millos]

Contributing

Pull requests are welcome. For major changes, please open an issue first to discuss what you would like to change.