Pete Gonzalez

What does this have to do with TSDoc?

Sure, sounds good to me. 🙂 I am on vacation this week but will have more time to investigate this next week.

Just to clarify, the PR would probably be for the `typescript-eslint` project, not `eslint-plugin-tsdoc`, right?

I haven't seen this configuration before. We should support it, but it hasn't ever been tested as far as I know. I won't have time to address it until after...

> In the sense of: "this should be possible" not "this seems like a bug", right? Ideally API Extractor should support every exotic usage of TypeScript imaginable, even if only...

Can you share a repro branch? In the previous discussion it seemed that ` "module": "none"` was causing the trouble. We expect an importable module with `export namespace Hmi {`....

`export default` is never a good practice, because the compiler isn't able to validate the name of the thing you are importing. For example you can accidentally have `import Dog...

> **Failing rollup (with default exports rollup not working):** > https://github.com/justintime4tea/ts-template/tree/default-exports-no-rollup This is failing because `export * from './Main';` ignores the default export in **Main.ts**. That construct only re-exports named...

Your relative paths are not a problem. It's bad to create a library where people need to use "**path-based imports**" like this: ```ts import { Something } from 'some-library/folder1/folder2/Something'; ```...

@andykais https://github.com/microsoft/web-build-tools/issues/664 tracks support for path-based imports. We do want to support it. It's a nontrivial feature, though. How do you represent them in the docs? For the .d.ts rollup,...