Paul

it is an error coming from the `rollup-plugin-typescript2` which is why it is prefixed with `rpt2`. It is because there is no tsconfig.json and nowhere in the rollup config do...

@cowboyd oh right so the error is that it cannot find any typescript files. I wanted to avoid us deciding if it is a typescript or javascript project

stdout or stderr from [here](https://github.com/ezolenko/rollup-plugin-typescript2/blob/42173460541b0c444326bf14f2c8c27269c4cb11/src/parse-tsconfig.ts#L51).

a couple of things we could do is: ```ts const isTypescript = fs.existsSync(process.cwd(), 'tsconfig.json); ``` Not sure if we can guarantee that but might be fine The error message is...

if it is typescript, we either disable the plugin or do not add it to the plugins array

@minkimcello this is different than #803. this is when there are no typescript files, i.e it is a javascript project but the rollup tyoescript2 plugin is still included in the...

I personally think insisting on a default export is problematic and I think we should work with named exports. Default exports in typescript are not the norm which in someway...

> We would need a "magic" named export I was forgetting about the reason why. That is tricky and would possibly need some AST trickery to cure it. The default...

this will also obviously fail as there are no `assertions` and `children` to map over: ```ts module.exports = { description: 'no assertions or children'; } ```

This has been closed by #13112