Empty declaration file when processing entry points using export = class about dts-bundle-generator HOT 3 CLOSED

Good news: I found the reason of this bug - it is wrong detecting that some node is exported, if it is exported via export =.

Bad news: this bug can be fixed after (or together with) #17.

from dts-bundle-generator.

Hi,

The export = Cache is the only way I found that allows to use the library in the same way in both Typescript and Javascript

But why not export { Cache } from './lib/main'; (or even export * from './lib/main';) and then import { Cache } from 'mylib';?

But anyway, it seems that it is easy to reproduce, but I need some time to investigate this problem and figure out the solution.

from dts-bundle-generator.

@timocov export = Cache is the only way I found (after researching a lot) that allows to use the library in in the same way in Javascript and Typescript.
If I use export { Cache } from './lib/main' or export * from './lib/main' then in Typescript it works but when transpiled to Javascript I must make an instance in a different way:

const Cache = require('easy-cache').Cache;
const cache = new Cache();

or

const Cache = require('easy-cache');
const cache = new Cache.Cache();

By the way I just tested version 1.6.0 with same results.

from dts-bundle-generator.