Nested namespace identifiers errors with namespace must have a "ModuleBlock" body

[kraenhansen]

Checklist

• I can reproduce this issue when running this plugin on its own.
  Other plugins, such as node-resolve are known to cause issues.
• I am running this plugin on .d.ts files generated by TypeScript.
  The plugin can consume .ts and even .js files (with allowJs: true), but this is known to cause issues.
• This issue is not related to rolling up @types.
  The plugin ignores these by default, unless respectExternal is set. @types can contain hand-crafted code which is known to cause issues.

Code Snipped

declare namespace Foo.Bar {}

Error Message

Error: namespace must have a "ModuleBlock" body.

Details

I get this error when using the shorthand for nesting namespaces (separating identifiers with dots).

I believe this is a more general case of #160.

Looking at the AST for this, the body of the first ModuleDeclaration is indeed another ModuleDeclaration and not a ModuleBlock as expected by the plugin.

Patching the default value of relaxedModuleBlock to true seems to solve the problem, but what would the drawback of that be?

[kraenhansen]

This too. How was it "completed", when was / is the fix released?

[Swatinem]

I mass-closed all the issues, as I transition the project into maintenance mode and won’t be working on any of it, see #277
However I wasn’t able to mass-close-and-comment mentioning that.

[kraenhansen]

Sure - I get the feeling of not having the time to drive actively drive project.
I do however find it a bit misleading that you're close issues, especially as "completed"?
Why not keep them around for others to find and contribute fixes for, as you're stating you welcome