I'm also trying to use tsd to test non-trivial generics/types in the source code of a project written in TypeScript. It would be nice if tsd directly supported an option to NOT require a .d.ts file, and NOT assume that it should try to load the file specified by package.json's "types" field (because that refers to a generated compiler output file for my project that either doesn't exist or is outdated at the time I attempt to run tsd).

But for now, I have come up with a hackish workaround.

WORKAROUND!!!

In my project, I added a dummy nested "project" directory named tsd_project. This directory contains a completely empty dummy.d.ts file and a package.json file that contains only this:

{
    "types": "dummy.d.ts",
    "tsd": {
        "directory": "../src"
    }
}

Then my script in my real package.json for running tsd references that fake project directory:

{
   "scripts": {
       "tsd": "tsd tsd_project"
   }
}

This satisfies tsd's current requirement to work in terms of a .d.ts file as specified by package.json, while looking for test files (.test-d.ts) in my project's src directory, so I can place test files adjacent to corresponding source files. Within my test files, I import directly from my source files with relative paths.

Uh oh!

How to write tests for source code in .ts files? #32

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions