Anton Gilgur

Does `tsc` not give this error? Type declaration files are ambient, as far as I know, you don't import them, you just `include` them in your build. That's why you...

TSDX's default `tsconfig` has an `include` (`typeRoots` or some other configs work for that too) for the `types` directory which is where you could put it

> @agilgur5 Thanks for the quick and thoughtful responses! I'll reply to each of your comments separately Thanks for the detailed reproduction, makes it easier to respond that way. One...

> It looks like the prettier + estlint config out of the box with tsdx doesn't like that syntax, though. > > Any idea how to fix this linting error...

> Might need to update the `resolve` plugin's configuration to add `.d.ts` as extension, which would explain why the error is "unable to resolve" So I thought I'd need to...

@0xpelmeni any `import type` statements should be ellided/removed by TS during compilation to JS as they don't exist in JS (plain `import` statements are different). You can also use a...

Thanks those details are helpful. > Currently in Project 1 `tsdx build` works fine and i'm able to publish the npm package and pull it in Project 2 and make...

> And for the advice, so I should copy the `.d.ts` files into `dist/` after `tsdx build` or before? Could do either, but might be easier after `tsdx build` in...

Thought I should add some notes here around some investigations and concerns I had over the past few months. ## Performance is not necessarily better when threaded/forked This is the...

Wanted to note here that there is an older, alpha, unmaintained plugin: [`rollup-plugin-fork-ts-checker`](https://github.com/fi3ework/rollup-plugin-fork-ts-checker). This plugin was designed to work with rpt2 and actually uses [the Webpack plugin under-the-hood](https://github.com/fi3ework/rollup-plugin-fork-ts-checker/blob/cd5f535168726ea65bde5f103dadce4300d9c3d6/src/ForkTsCheckerPlugin.ts#L19). The author...