"Could not load TypeScript. Try installing with `npm install -g typescript`"

[ldminoc]

I updated to 0.5.2 from 0.5.0 this morning but still seem to be having the same issue although the new error message is less useful for problem identification. After receiving the error message, I updated typescript to the latest nightly build using 'npm install -g typescript@next'.

Any insights would be appreciated.

Here's my webpack.config.js:

'use strict';

var webpack = require('webpack');
var WebpackNotifierPlugin = require('webpack-notifier');

module.exports = {
  entry: './server/server.ts',
  output: {
    path: './build/',
    filename: 'server.js'
  },
  plugins: [
    new webpack.optimize.OccurenceOrderPlugin(),
    new WebpackNotifierPlugin()
  ],
  resolve: {
    extensions: ['', '.webpack.js', '.web.js', '.js', '.jsx', '.ts', '.tsx']
  },
  module: {
    loaders: [
      {
        test: /\.jsx$/,
        exclude: ['./node_modules/'],
        loader: 'babel-loader'
      },
      {
        test: /\.ts(x?)$/,
        exclude: ['./node_modules/'],
        loader: 'ts-loader'
      }
    ]
  }
};

And here is the tsconfig.js:

{
    "compilerOptions": {
        "module": "commonjs",
        "noImplicitAny": true,
        "removeComments": true,
        "preserveConstEnums": true,
        "target": "ES5",
        "sourceMap": true
    }
}

With 0.5.0, the error message was:
ERROR in ./server/server.ts

Module build failed: Error: Cannot find module 'typescript'
at Function.Module._resolveFilename (module.js:336:15)
at Function.Module._load (module.js:278:25)
at Module.require (module.js:365:17)
at require (module.js:384:17)
at ensureTypeScriptInstance (partial path elided .../node_modules/ts-loader/index.js:69:20)
at Object.loader (partial path elided .../node_modules/ts-loader/index.js:228:14)

[jbrantly]

In both cases it just means that node can't resolve typescript for some reason. Usually if you have it installed globally it will "just work", which is why there is the new message in 0.5.2. You could try installing locally. Go to your project root and use npm install typescript. Maybe there is some weird configuration that is preventing node from being able to resolve typescript globally. I've run into weird resolution issues in the past on Windows with older versions of node. Maybe try updating node and npm if the local install doesn't work.

[ldminoc]

Wow impressive response time!
Your suggestion of installing typescript locally works, but it does not feel like a very satisfying solution ;-).
I'm running node v0.12.6, npm 2.11.2 on a mac so have no idea what the issue is.
Thanks for the help.

[jbrantly]

It's possible I should change the messaging to "Please install using npm install typescript" instead based on this. In any case, glad it's working for you.

[ldminoc]

Sorry, should have closed this earlier.

[jbrantly]

No worries :)

[jbrantly]

FYI, I changed the message in the latest release to no longer have the -g flag.

[OldrichDlouhy]

Another approach that worked for me is to install typescript globally (npm install -g typescript) and then link to it from the local folder (npm link typescript).

[jbrantly]

Just for documentation purposes: The preferGlobal flag was removed in TS 1.6.

[slavovojacek]

@OldrichDlouhy linking through npm link typescript works perfectly, thanks!

[ArgTang]

@jbrantly
I found the link option that is suggested as a noce solution thats more elegant, when typescript is installed globally. maybe change the message again to reflect this?

[jbrantly]

@ArgTang sure, sounds good.