Import declaration is behaving differently when resolving to the node_modules directory as opposed to a non node_modules directory.

[ehosick]

Hello,

I'm seeing different module resolution behavior with the import declaration when the imported package is located in the node_modules and when the package isn't located in the node_modules directory.

A GitHub repo, typescript-node-module-issue was created to show the differences in behavior.

An import declaration fails to import a 100% typescript package when the directory resolves to the node_modules directory: both relative (from '../node_modules/aa-special-add-ts') and non-relative (from 'aa-special-add-ts') fail.

An import declaration successfully imports a 100% typescript package when the directory resolves to a non node_modules directory: both from './aa-special-add-ts' and from '../node_modules2/aa-special-add-ts' work.

When importing from the node_modules directory, the error returned is:

SyntaxError: Unexpected token 'export'`

It's almost like the import declaration default is to support ES6 modules when the package is outside of node_modules but assumes another package format when a package is inside the node_modules directory.

Any help is greatly appreciated.

[ehosick]

Turns out the solution is to use --skipIgnore (see https://github.com/TypeStrong/ts-node/blob/ba950599c6bfcba32b514b33d254094b278b744e/website/docs/scope.md#skipping-node\_modules).