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

type-tester

v1.0.0

Published

A tester to check expected type errors

Downloads

1,148

Readme

type-tester

npm version Downloads/month Build Status Coverage Status Dependency Status

A tester to check expected type errors.

🏁 Goal

This package provides utility to verify that the type you have written stricter reports expected type errors, for TypeScript.

💿 Installation

Use npm or a compatible tool to install this package.

npm install type-tester typescript
  • Requires Node.js >=6.0.0.

📖 Usage

  1. Write fixture files.
  2. Write test files.
  3. Run test files with test runner such as mocha.

1. Write fixture files.

The fixture file should include the situation of type error. You must add directive comments such as // @expected 2345 for each line of expected errors. The number is the error code of TypeScript.

For example: test/fixtures/event-target-shim/fixture.ts

2. Write test files.

The test file should execute TypeTester#verify() method with the path to the fixture files and compiler options.

For example: test/example.ts

3. Run test files with test runner such as mocha.

Because the TypeTester#verify() method defines test cases with describe / it global functions, you must run it with test runners.

For example:

mocha test/example.ts --require ts-node/register

  this test runs the type tester merely.
    fixture.ts
      √ should have an error TS2345 at L98.
      √ should have an error TS2345 at L101.
      √ should have an error TS7006 at L102.
      √ should have an error TS2345 at L105.
      √ should have an error TS7006 at L106.
      √ should have an error TS2322 at L108.
      √ should have an error TS2322 at L109.
      √ should have an error TS2345 at L152.

  8 passing (11ms)

📚 API References

TypeTester class

The class to verify expected type errors.

constructor(ts: typeof import("typescript"), options: TypeTester.Options)

Parameters

Name | Description :----|:----------- ts | API to use type checking. options.describe | Optional. Function to declare test suites. Use global.describe by default. options.it | Optional. Function to declare test cases. Use global.it by default.

tester.verify(fixtureFiles: ReadonlyArray<string>, compilerOptions: ts.CompilerOptions): void

Verify the given fixture files.

Parameters

Name | Description :----|:----------- fixtureFiles | Path to fixture files. compilerOptions | Compiler options to verify the fixture files.

📰 Release notes

  • https://github.com/mysticatea/type-tester/releases

❤️ Contributing

Contribution is welcome!

Please use GitHub issues and pull requests.

Development tools

  • npm run build generates files into dist directory.
  • npm run clean removes temporary files.
  • npm run coverage opens the coverage report the last npm test command generated.
  • npm run lint runs ESLint.
  • npm test runs tests.
  • npm run watch runs tests on each file edits.