Anton Gilgur

Results 284 comments of Anton Gilgur

Copying from something Jared said in #118 almost a year ago: > I think someone tried to solve this in #75, but this generated absolute paths to tsdx's jest plugins....

So I looked through the [`rollup/plugins`](https://github.com/rollup/plugins) repo (including things like [validation source code](https://github.com/rollup/plugins/blob/556837f0b7e7323f237370e36394569abc2b1ef9/packages/babel/src/preflightCheck.js)) to see if there was an official / standard way of doing schema validation in plugins, but...

Recently found https://github.com/moltar/typescript-runtime-type-benchmarks and figured I'd notate some more here. While the benchmarks themselves aren't super relevant for our use-case given that they'd only run once per build, the repo...

So I'm not sure why this works in v0.9.0, but not v0.13.3, but TSDX doesn't do its own TS parsing, that's delegated to `rollup-plugin-typescript2`, so per the label, this sounds...

Per the error, that would be because your `tsconfig.json`'s [`target`](https://www.typescriptlang.org/tsconfig#target) setting isn't `ES5` or above. That might be because you used the [templates](https://github.com/jaredpalmer/tsdx/blob/2d7981b00b2bf7363a3eeff44ff5ff698ba58c8c/templates/react-with-storybook/tsconfig.json), which don't have a `target` setting since...

Thanks for filing a detailed issue and adding a workaround @luxaritas! > This may be the actual issue raised in #294 Good to know! It was closed by the OP...

> I'm well aware that this plugin is designed for Rollup and note Vite, hence my note that I had considered filing an issue against Vite instead. And I was...

Possible duplicate of #271, which was recently fixed by #364, but hasn't been released yet (looking to do a release very soon, though I don't have publishing permissions)

#364 has been released in [`0.33.0`](https://github.com/ezolenko/rollup-plugin-typescript2/releases/0.33.0.1) I confirmed in your repro that with `0.33.0` the error is no longer present, so this indeed turns out to be a duplicate of...

Hi folks, just doing some housekeeping in the issues. I'm going to close this one out as it's gone quite stale (no comments in 2+ years) and only has one...