Using the documented way to import the current pattern to use it in a demo fails, because module 'Pattern' cannot be resolved.

import Button from 'Pattern'

leads to

demo.tsx (2,24): Cannot find module 'Pattern'

Also imports from referenced Patterns in pattern.json, lead to a console-error, which are apparently irrelevant, because the Pattern is displayed correctly in patternplate frontend.

For patterns that do compile, but have an error during declaration generation, the generation completes without an error, but sadly without a generated index.d.ts file.

type RGB = [number, number, number];

type ColorOptions = {
  displayName: string;
  rgb: RGB;
};

export default ColorOptions;

This transpiles correctly to a nearly empty index.js with tsc on the commandline. Generating the declaration with -d option fails correctly, because of
error TS4081: Exported type alias 'ColorOptions' has or is using private name 'RGB'.

patternplate-transform-typescript does not emit this error (console/exit code) and generates no d.ts-file silently.

We are trying to execute the build task. Some patterns (not all of them) are not receiving the proper typing definitions. This includes the module exports too.

Dev Pattern

This is an example of one of the develop patterns.

Compiled Pattern

This would be the compilation result.

As you can see, the exports do not include the typings of the components. What might be important to note is that the compiled d.ts is actually the typing and exports of a completely different component (see below screenshot).

For external packages shipping with index.d.ts files such as [email protected] transform-typescript produces the following error:

Cannot read property 'pattern' of undefined
at ~/node_modules/patternplate-transform-typescript/dist/transpiler.js:82:58
at Array.map (native)

Digging in a bit deeper reveals this is caused by transform-typescript trying to access properties on a null Object obtained by accessing ~/node_modules/styled-components/typings/styled-components.d.ts on map in compilerHost.resolveModuleNames.

resolve dependency path are not respected in generated type definitions.