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

@vta/tsc

v1.1.4

Published

compile Typescript files to Javascript files using Typescript and Babel

Downloads

19

Readme

@vta/tsc

compile Typescript files to Javascript files using Typescript and Babel

npm Build Status codecov

Install

npm install --save-dev @vta/tsc
// or using yarn
yarn add @vta/tsc --dev

Usage

using in cli

{
  "scripts": {
    "build": "vta-tsc src --out-dir dist -p tsconfig.json -b babel.config.js"
  }
}

using in js files

const { default: tsc } = require("@vta/tsc");

tsc({
  sourceDir: "src",
  outDir: "dist",
  project: "tsconfig.json",
  babel: "babel.config.js",
  // ...options
}).then(err => {
  if (err) {
    console.log(`build error :${err.message}`);
    return;
  }
  console.log("build successfully");
});

Options

export interface TscOption {
  sourceDir?: string;
  outDir?: string;
  project?: string;
  babel?: string | false;
  esnext?: boolean;
  extTs?: string;
  extJs?: string;
  exclude?: string[];
  silent?: boolean;
  cwd?: string;
}

all paths are relative to your working directory cwd

sourceDir

the directory to compile files from. default is src

when using cli,the first argument is sourceDir

outDir,--out-dir

the directory to compile files to. default is dist

project,--project,-p

typescript config file. default is tsconfig.json

babel,--babel,-b,--no-babel

babel config file. default is babel.config.js

if you donn't want to compile files using Babel,please set this to false, or using --no-babel in cli

esnext,--no-exnext

compile Typescript files to esnext target. default is true

this is important to compile using Babel,if not,please set this to false or using --no-esnext in cli

extTs,--ext-ts

the extensions that compile using Typescript,split by ,. default is ts

extJs,--ext-js

the extensions that compile using Babel,split by ,. default is js

exclude,--exclude

the patterns of glob to exclude. split by , for cli usage;

silent --silent

do not display any except error message. default is false

cwd

working directory. default is .

MIT License