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

@hint/parser-typescript-config

v2.4.31

Published

webhint parser needed to analyze TypeScript config files

Downloads

76,728

Readme

TypeScript config (@hint/parser-typescript-config)

The typescript-config parser allows the user to analyze the TypeScript configuration in their projects.

It will detect if a TypeScript configuration file is present in your project, checking the name of the file (i.e. tsconfig.json, tsconfig.developement.json). This parser detects if a config file has a valid content.

This package is installed automatically by webhint:

npm install hint --save-dev

To use it, activate it via the .hintrc configuration file:

{
    "connector": {...},
    "formatters": [...],
    "hints": {
        ...
    },
    "parsers": ["typescript-config"],
    ...
}

Note: The recommended way of running webhint is as a devDependency of your project.

Events emitted

This parser emits the following events:

  • parse::start::typescript-config, of type TypeScriptConfigParseStart which contains the following information:

    • resource: the resource we are going to parse.
  • parse::end::typescript-config, of type TypeScriptConfigParse which contains the following information:

    • resource: the parsed resource.
    • getLocation: helper to find the location of a path within the original JSON source.
    • config: the final configuration after adding default values (TypeScriptConfig).
    • mergedConfig: the merged configuration after inlining extends.
    • originalConfig: the original configuration before resolving extends.
  • parse::error::typescript-config::json, of type TypeScriptConfigInvalidJSON which contains the following information:

    • resource: the parsed resource.
    • error: the error emited parsing the configuration file.
  • parse::error::typescript-config::cicular, of type TypeScriptConfigInvalidJSON which contains the following information:

    • resource: the parsed resource.
    • error: the error emited parsing the configuration file.
  • parse::error::typescript-config::extends, of type TypeScriptConfigInvalidJSON which contains the following information:

    • resource: the parsed resource.
    • error: the error emited parsing the configuration file.
  • parse::error::typescript-config::schema, of type TypeScriptConfigInvalidSchema which contains the following information:

    • resource: the parsed resource.
    • errors: all the errors that the schama validator returns.

Types

If you need to import any type or enum defined in this parser, you need to import them as follows:

import { TypeOrEnumYouWantToUse } from '@hint/parser-typescript-config';