Symlinked node_modules directory confuses dts-bundle-generator

I have to admit, this is probably a quite uncommon use case, but still wanted to report it because maybe it can be fixed easily.

This is based on the same example as #37. Rename your node_modules directory and symlink it:

mv node_modules .node_modules_develop
ln -s .node_modules_develop node_modules

Then extract the typings. You will get a huge definitions file with a lot of inlined types. It seems like the symlink is confusing the logic that figures out how to deal with a dependency.

I’ve been using the symlink for a long time now as a technique to make it easy and fast to switch between the modules required for my develop and release branches. It hasn’t caused any problems with NPM itself or other tools so far.

[rhuitl]

Yes, of course. Create a new directory. Place these files:

app.ts

export function test(): void { }

package.json

{
  "name": "dts-bundle-generator-bugreport",
  "version": "1.0.0",
  "private": true,
  "scripts": {
    "build": "tsc",
    "typings": "dts-bundle-generator --verbose --disable-symlinks-following -o app.d.ts app.ts"
  },
  "dependencies": {},
  "devDependencies": {
    "dts-bundle-generator": "^1.5.0",
    "typescript": "^2.9.1"
  }
}

tsconfig.json

{
  "compilerOptions": {
    "target": "es5",
    "declaration": true,
    "lib": ["es2015", "dom"]
  },
  "files": ["app.ts"]
}

Run npm install Run npm run typings, look at console output and the generated typings file which look like they should.

Move the node_modules directory and symlink it:

mv node_modules foobar
ln -s foobar node_modules

Run npm run typings again, this time the console has a lot of output and the typings file contains typings from es2015 and dom.

[timocov]

Version 1.6.0 is published.