typings always complaining about global module

module typescript global external
ironic picture ironic · May 21, 2016 · Viewed 7.7k times · Source

I am very new to typescript. Whatever typings I try to install, I get:

typings ERR! message Attempted to compile "angular" as an external module, but it looks like a global module.

I am just trying to do

typings install dt~angular

What am I doing wrong?

Update: If you are coming here with little knowledge (as I was when writing this question) - consider using npm/@types. More info and discussion.

Answer

Andrey Chausenko picture Andrey Chausenko · May 23, 2016

As error message suggests, you should use --global option:

typings install dt~angular --global --save

See detailed step-by-step tutorial for setting up Node.js project with TypeScript support in IntelliJ IDEA / Webstorm or Visual Studio Code

TypeScript and tools around it are evolving very fast. What worked yesterday don't work any more.

Related questions

Typescript ReferenceError: exports is not defined

Trying to implement a module following the official handbook, I get this error message: Uncaught ReferenceError: exports is not defined at app.js:2 But nowhere in my code do I ever use the name exports. How can I fix this? …

Read More
How do I use namespaces with TypeScript external modules?

I have some code: baseTypes.ts export namespace Living.Things { export class Animal { move() { /* ... */ } } export class Plant { photosynthesize() { /* ... */ } } } dog.ts import b = require('./baseTypes'); export namespace Living.Things { // Error, can't find name 'Animal', ?? export class Dog extends Animal { woof() { } } } …

Read More
Why does Typescript use the keyword "export" to make classes and interfaces public?

While dabbling with Typescript I realised my classes within modules (used as namespaces) were not available to other classes unless I wrote the export keyword before them, such as: module some.namespace.here { export class SomeClass{..} } So now I can …

Read More