Typescript error Cannot find module 'typescript-Collections' when changing the module to "umd" or "amd" in tsconfig.json

Question

I am using VS17 Enterprise. I can easily import "typescript-collections" (as instructed on this page) if I had set my module option to commonjs in my tsconfig.json.

However, as soon as I change it to "umd" or "amd", I get error (see the screenshot please) saying that Cannot find module 'typescript-collections' and therefore, the two variables queue and queue1 will be of type any. I have also attached my tsconfig.json.

Any help will be greatly appreciated.

Hey, I'm also having this issue! Did you ever figure this out? — rassar, Aug 23 '18 at 17:12
@SadraAbedinzadeh Is there a particular reason you want to use `umd` or `amd` module resolution? — xiaodeaux, Dec 08 '18 at 04:22
@xiaodeaux, No, but why not? If i change my settings to use `amd` or `commonJs` some other modules will throw errors. Isn't it true that the whole point of using `umd` is to get rid of these problems ? — Sadra Abedinzadeh, Dec 21 '18 at 19:41

score 0 · Answer 1 · answered Apr 14 '19 at 12:17

0

As of today this problem with this package remains and my solution was to use es6 as my module

{
  "extends": "../tsconfig.json",
  "compilerOptions": {
    "outDir": "../out-tsc/app",
    "types": [],
    "module":"es6"
  },
  "exclude": [
    "test.ts",
    "**/*.spec.ts"
  ]
}

and then import the classes using the notation below -

import * as Collections from 'typescript-collections/src/lib';

It seems there is an issue with this dependency packaging.

answered Apr 14 '19 at 12:17

Gautam

1,030
13
37

even this results in compilation error i.e. index.ts needs to be a part of the package or similar error message. I ended up copying all the classes to my project source folder to use it. – Gautam Apr 16 '19 at 08:21

score 0 · Answer 2 · answered Mar 10 '20 at 16:08

I fixed a similar problem by explicitly specifying the moduleResolution compiler option.

{
    "compilerOptions":
    {
        "moduleResolution": "node"
    }
}

Apparently the moduleResolution is set to "node" automatically, if module is set to "commonjs". The Typescript compiler seems to use another resolution strategy otherwise.

A post in a GitHub issue thread led me to this idea.

Typescript error Cannot find module 'typescript-Collections' when changing the module to "umd" or "amd" in tsconfig.json

2 Answers2