Collectives™ on Stack Overflow

Find centralized, trusted content and collaborate around the technologies you use most.

Teams

Q&A for work

Connect and share knowledge within a single location that is structured and easy to search.

I am having a hard time trying to get the lodash modules imported. I've setup my project using npm+gulp, and keep hitting the same wall. I've tried the regular lodash, but also lodash-es.

The lodash npm package: (has an index.js file in the package root folder)

import * as _ from 'lodash';    
Results in:
error TS2307: Cannot find module 'lodash'.
The lodash-es npm package: (has a default export in lodash.js i the package root folder)
import * as _ from 'lodash-es/lodash';
Results in:
error TS2307: Cannot find module 'lodash-es'.   
Both the gulp task and webstorm report the same issue.
Funny fact, this returns no error:
import 'lodash-es/lodash';
... but of course there is no "_" ...
My tsconfig.json file:
  "compilerOptions": {
    "target": "es5",
    "module": "system",
    "moduleResolution": "node",
    "sourceMap": true,
    "emitDecoratorMetadata": true,
    "experimentalDecorators": true,
    "removeComments": false,
    "noImplicitAny": false
  "exclude": [
    "node_modules"
My gulpfile.js:
var gulp = require('gulp'),
    ts = require('gulp-typescript'),
    uglify = require('gulp-uglify'),
    sourcemaps = require('gulp-sourcemaps'),
    tsPath = 'app/**/*.ts';
gulp.task('ts', function () {
    var tscConfig = require('./tsconfig.json');
    gulp.src([tsPath])
        .pipe(sourcemaps.init())
        .pipe(ts(tscConfig.compilerOptions))
        .pipe(sourcemaps.write('./../js'));
gulp.task('watch', function() {
    gulp.watch([tsPath], ['ts']);
gulp.task('default', ['ts', 'watch']);
If I understood correctly, moduleResolution:'node' in my tsconfig should point the import statements to the node_modules folder, where lodash and lodash-es are installed. I've also tried lots of different ways to import: absolute paths, relative paths, but nothing seems to work. Any ideas?
If necessary I can provide a small zip file to illustrate the problem.
                I ran into this problem too.  The lodash library does not have typecript definitions included in modular format so the import statements do not work. The only work around now it seems is make a script reference to lodash in your index.html file then reference the lodash.d.ts in your typescript files.  hopefully this will be fixed soon.  if there is another work around for this i would like to hear it.
– brando
                Jan 7, 2016 at 16:45
                the zip file would be great. But it looks like you are not using any module loader (like jspm or webpack) ? How are you loading Angular, via script tags? better post the html as well. I recommend you use webpack as module loader, see here an example -> github.com/jhades/angular2-library-example/tree/master/examples/… and this is a minimal starter -> github.com/jhades/ng2-webpack-minimal
– Angular University
                Jan 7, 2016 at 16:49
                I ended up just adding this to my mail ts file:    /// <reference path="../typings/tsd.d.ts" />
– Davy
                Jan 18, 2016 at 12:30
Here is how to do this as of Typescript 2.0:
(tsd and typings are being deprecated in favor of the following):
$ npm install --save lodash
# This is the new bit here: 
$ npm install --save-dev @types/lodash
Then, in your .ts file: 
Either:
import * as _ from "lodash";
Or (as suggested by @Naitik):
import _ from "lodash";
I'm not positive what the difference is. We use and prefer the first syntax. However, some report that the first syntax doesn't work for them, and someone else has commented that the latter syntax is incompatible with lazy loaded webpack modules. YMMV.
Edit on Feb 27th, 2017:
According to @Koert below, import * as _ from "lodash"; is the only working syntax as of Typescript 2.2.1, lodash 4.17.4, and @types/lodash 4.14.53. He says that the other suggested import syntax gives the error "has no default export".
                I can confirm that this works when using typescript 2.0.3. Indeed removing typings in favor of @types npm package is much cleaner.
– Adrian Moisa
                Sep 23, 2016 at 14:56
                A word of warning, I've found the import _ from "lodash" syntax to be incompatible with lazy loaded webpack modules. Not sure why, I haven't investigated in detail.
– Tom Makin
                Oct 25, 2016 at 7:14
                import _ from "lodash"; doesn't work anymore in 2.0. You have to use import * as _ from "lodash";
– Roger Far
                Mar 6, 2017 at 2:30
                This should be used only in development, not production, so use save-dev:  npm install --save-dev @types/lodash  If you're seeing weird issues and bugs, try this:  npm install --save-dev @types/lodash@4.14.50
– leetheguy
                Apr 4, 2017 at 18:11
Update September 26, 2016:
As @Taytay's answer says, instead of the 'typings' installations that we used a few months ago, we can now use:
npm install --save @types/lodash
Here are some additional references supporting that answer:
https://www.npmjs.com/package/@types/lodash
TypeScript typings in NPM @types org packages
If still using the typings installation, see the comments below (by others) regarding '''--ambient''' and '''--global'''.
Also, in the new Quick Start, config is no longer in index.html; it's now in systemjs.config.ts (if using SystemJS).
Original Answer:
This worked on my mac (after installing Angular 2 as per Quick Start):
sudo npm install typings --global
npm install lodash --save 
typings install lodash --ambient --save
You will find various files affected, e.g.
/typings/main.d.ts
/typings.json
/package.json
Angular 2 Quickstart uses System.js, so I added 'map' to the config in index.html as follows:
System.config({
    packages: {
      app: {
        format: 'register',
        defaultExtension: 'js'
    map: {
      lodash: 'node_modules/lodash/lodash.js'
Then in my .ts code I was able to do:
import _ from 'lodash';
console.log('lodash version:', _.VERSION);
Edits from mid-2016: 
As @tibbus mentions, in some contexts, you need:
import * as _ from 'lodash';
If starting from angular2-seed, and if you don't want to import every time, you can skip the map and import steps and just uncomment the lodash line in tools/config/project.config.ts.
To get my tests working with lodash, I also had to add a line to the files array in karma.conf.js:
'node_modules/lodash/lodash.js',
                I see that this resolves my TypeScript issues, but loading the page in a browser I still see the error that it can't find module lodash. It looks like it's making a failed xhr request to '/lodash' instead of node_modules.
– Zack
                Apr 20, 2016 at 20:02
                @zack did you miss  map: {       lodash: 'node_modules/lodash/lodash.js'     }  in the System.config ?
– xwb1989
                May 4, 2016 at 17:56
                ...and why do we need to write import * as _ from 'lodash' instead of import _ from 'lodash' ?
– smartmouse
                Jul 13, 2016 at 16:29
                @smartmouse --ambient is a former for --global. The latter is used in 1.x and moving forward.  Though, I don't think the latest lodash 4.x will compile as global module like that.
– demisx
                Aug 5, 2016 at 21:00
// Load the full library...
import * as _ from 'lodash' 
// work with whatever lodash functions we want
_.debounce(...) // this is typesafe (as expected)
OR load only functions we are going to work with
import * as debounce from 'lodash/debounce'
//work with the debounce function directly
debounce(...)   // this too is typesafe (as expected)
UPDATE - March 2017
I'm currently working with ES6 modules, and recently i was able to work with lodash like so:
// the-module.js (IT SHOULD WORK WITH TYPESCRIPT - .ts AS WELL) 
// Load the full library...
import _ from 'lodash' 
// work with whatever lodash functions we want
_.debounce(...) // this is typesafe (as expected)
OR import specific lodash functionality:
import debounce from 'lodash/debounce'
//work with the debounce function directly
debounce(...)   // this too is typesafe (as expected)
NOTE - the difference being * as is not required in the syntax
References:
Good Luck.
                @Toolkit.  Thank you for pointing it out.  I have updated the answer.  Please check if this solutions works and mark appropriately.
– Aakash
                Dec 9, 2016 at 3:19
                import debounce from 'lodash/debounce' yields TS1192: Module node_modules/@types/lodash/debounce has no default export when "allowSyntheticDefaultImports": false
– kross
                Nov 22, 2017 at 16:08
                I stand by my previous comment. There is not currently a default export in the types file, so this does not work with allowSyntheticDefaultImports false.
– kross
                Nov 23, 2017 at 13:50
                @kross  Also note that adding the "allowSyntheticDefaultImports": true compiler option in your tsconfig.json file might be needed to avoid any error.
– Aakash
                Nov 30, 2017 at 10:24
"@angular/common":  "2.0.0-rc.1",
"@angular/compiler":  "2.0.0-rc.1",
"@angular/core":  "2.0.0-rc.1",
"@angular/http":  "2.0.0-rc.1",
"@angular/platform-browser":  "2.0.0-rc.1",
"@angular/platform-browser-dynamic":  "2.0.0-rc.1",
"@angular/router":  "2.0.0-rc.1",
"@angular/router-deprecated":  "2.0.0-rc.1",
"@angular/upgrade":  "2.0.0-rc.1",
"systemjs": "0.19.27",
"es6-shim": "^0.35.0",
"reflect-metadata": "^0.1.3",
"rxjs": "5.0.0-beta.6",
"zone.js": "^0.6.12",
"lodash":"^4.12.0",
"angular2-in-memory-web-api": "0.0.7",
"bootstrap": "^3.3.6"  }
Step 2:I am using SystemJs module loader in my angular2 application. So I would be modifying the systemjs.config.js file to map lodash.
(function(global) {
// map tells the System loader where to look for things
var map = {
    'app':                        'app', // 'dist',
    'rxjs':                       'node_modules/rxjs',
    'angular2-in-memory-web-api': 'node_modules/angular2-in-memory-web-api',
    '@angular':                   'node_modules/@angular',
    'lodash':                    'node_modules/lodash'
// packages tells the System loader how to load when no filename and/or no extension
var packages = {
    'app':                        { main: 'main.js',  defaultExtension: 'js' },
    'rxjs':                       { defaultExtension: 'js' },
    'angular2-in-memory-web-api': { defaultExtension: 'js' },
    'lodash':                    {main:'index.js', defaultExtension:'js'}
var packageNames = [
    '@angular/common',
    '@angular/compiler',
    '@angular/core',
    '@angular/http',
    '@angular/platform-browser',
    '@angular/platform-browser-dynamic',
    '@angular/router',
    '@angular/router-deprecated',
    '@angular/testing',
    '@angular/upgrade',
// add package entries for angular packages in the form '@angular/common': { main: 'index.js', defaultExtension: 'js' }
packageNames.forEach(function(pkgName) {
    packages[pkgName] = { main: 'index.js', defaultExtension: 'js' };
var config = {
    map: map,
    packages: packages
// filterSystemConfig - index.html's chance to modify config before we register it.
if (global.filterSystemConfig) { global.filterSystemConfig(config); }
System.config(config);})(this);
Step 3: Now  do npm install
Step 4: To use lodash in your file. 
import * as _ from 'lodash';
let firstIndexOfElement=_.findIndex(array,criteria);
                How does your solution take care of the TypeScript typings? The npm lodash package does not seem to include the .d.ts files.
– Vitali Kniazeu
                Jul 11, 2016 at 14:09
Since Typescript 2.0, @types npm modules are used to import typings.
# Implementation package (required to run)
$ npm install --save lodash
# Typescript Description
$ npm install --save @types/lodash 
Now since this question has been answered I'll go into how to efficiently import lodash
The failsafe way to import the entire library (in main.ts)
import 'lodash';
This is the new bit here:
Implementing a lighter lodash with the functions you require
import chain from "lodash/chain";
import value from "lodash/value";
import map from "lodash/map";
import mixin from "lodash/mixin";
import _ from "lodash/wrapperLodash";
source: https://medium.com/making-internets/why-using-chain-is-a-mistake-9bc1f80d51ba#.kg6azugbd
PS: The above article is an interesting read on improving build time and reducing app size
                For TSC this is great, however it gives other issues with bundlers. any chance you managed to get this working through rollup? aurelia-cli also gives issues with it :(.  Rollup error: 'default' is not exported by node_modules\lodash\kebabCase.js  Aurelia cli error:  no such file or directory, open '/experimental\au-proj\node_modules\lodash\lodash\kebabCase.js'
– Stephen Lautier
                Nov 15, 2016 at 1:43
                Seems the @types/lodash doesn't support the lighter syntax yet.   error TS1192: Module '"node_modules/@types/lodash/chain/index"' has no default export.  And so forth for other modules attempting the shorter import chain from "lodash/chain" imports
– jamsinclair
                Jan 23, 2017 at 2:57
I successfully imported lodash in my project with the following commands:
npm install lodash --save
typings install lodash --save
Then i imported it in the following way:
import * as _ from 'lodash';
and in systemjs.config.js i defined this:
map: { 'lodash' : 'node_modules/lodash/lodash.js' }
I had exactly the same problem, but in an Angular2 app, and this article just solve it: https://medium.com/@s_eschweiler/using-external-libraries-with-angular-2-87e06db8e5d1#.p6gra5eli 
Summary of the article:
Installing the Library npm install lodash --save
Add TypeScript Definitions for Lodash tsd install underscore
Including Script <script src="node_modules/lodash/index.js"></script>
Configuring SystemJS System.config({
          paths: {
              lodash: './node_modules/lodash/index.js'
Importing Module import * as _ from ‘lodash’;
I hope it can be useful for your case too
Another elegant solution is to get only what you need, not import all the lodash
import {forEach,merge} from "lodash";
and then use it in your code
forEach({'a':2,'b':3}, (v,k) => {
   console.log(k);
                Does this actually work? I've tried this and it doesn't seem to change the size of the bundle.
– Cody
                Feb 16, 2017 at 14:06
                @Pian0_M4n maybe i'm doing it wrong but tried with angular cli 1.4.4 tree shaking didn't work
– alexKhymenko
                Oct 2, 2017 at 8:39
                @Pian0_M4n there is no error, just no tree shaking. It loads the whole library not forEach and merge methods.
– alexKhymenko
                Oct 2, 2017 at 13:34
If anyone else runs into this issue and none of the above solutions work due to "Duplicate identifier" issues, run this:
npm install typings --global
With older versions of typings things mess up and you'll get a bunch of "Duplicate identifier" issues. Also you don't need to use --ambient anymore as far as I could tell.
So once typings is up to date, this should work (using the Angular 2 quickstart).
npm install lodash --save 
typings install lodash --save
First, add this to systemjs.config.js:
'lodash':                     'node_modules/lodash/lodash.js'
Now you can use this in any file: import * as _ from 'lodash';
Delete your typings folder and run npm install if you're still having issues.
Please note that npm install --save will foster whatever dependency your app requires in production code.

As for "typings", it is only required by TypeScript, which is eventually transpiled in JavaScript. Therefore, you probably do not want to have them in production code. I suggest to put it in your project's devDependencies instead, by using
npm install --save-dev @types/lodash
npm install -D @types/lodash
(see Akash post for example). By the way, it's the way it is done in ng2 tuto.
Alternatively, here is how your package.json could look like:
    "name": "my-project-name",
    "version": "my-project-version",
    "scripts": {whatever scripts you need: start, lite, ...},
    // here comes the interesting part
    "dependencies": {
       "lodash": "^4.17.2"
    "devDependencies": {
        "@types/lodash": "^4.14.40"
just a tip
The nice thing about npm is that you can start by simply do an npm install --save or --save-dev if you are not sure about the latest available version of the dependency you are looking for, and it will automatically set it for you in your package.json for further use.
Partial import from lodash should work in angular 4.1.x using following notation:
let assign = require('lodash/assign');
Or use 'lodash-es' and import in module:
import { assign } from 'lodash-es';
                import { assign } from 'lodash-es'; seems to still import the whole library (judging by bundle size)
– ihor.eth
                Sep 18, 2019 at 22:42
I had created typings for lodash-es also, so now you can actually do the following
install
npm install lodash-es -S
npm install @types/lodash-es -D
usage
import kebabCase from "lodash-es/kebabCase";
const wings = kebabCase("chickenWings");
if you use rollup, i suggest using this instead of the lodash as it will be treeshaken properly.
sudo npm install typings --global
npm install lodash --save 
typings install lodash --ambient --save
In index.html, add map for lodash:
System.config({
    packages: {
      app: {
        format: 'register',
        defaultExtension: 'js'
    map: {
      lodash: 'node_modules/lodash/index.js'
In .ts code import lodash module

import _ from 'lodash';
                It is throwing error:  $ typings install lodash --ambient --save typings ERR! message https://api.typings.org/entries/npm/lodash/versions/latest responded with 407, expected it to equal 200
– kamayd
                May 20, 2016 at 14:52
I am using ng2 with webpack, not system JS. Steps need for me were:
npm install underscore --save
typings install dt~underscore --global --save
and then in the file I wish to import underscore into:
import * as _ from 'underscore';
Managing types via typings and tsd commands is ultimately deprecated in favor of using npm via npm install @types/lodash.
However, I struggled with "Cannot find module lodash" in import statement for a long time:
import * as _ from 'lodash';
Ultimately I realized Typescript will only load types from node_modules/@types start version 2, and my VsCode Language service was still using 1.8, so the editor was reporting errors. 
If you're using VSCode you'll want to include 
"typescript.tsdk":  "node_modules/typescript/lib"
in your VSCode settings.json file (for workspace settings) and make sure you have typescript version >= 2.0.0 installed via npm install typescript@2.0.2 --save-dev
After that my editor wouldn't complain about the import statement.
I'm on Angular 4.0.0 using the preboot/angular-webpack, and had to go a slightly different route.
The solution provided by @Taytay mostly worked for me:
npm install --save lodash
npm install --save @types/lodash
and importing the functions into a given .component.ts file using:
import * as _ from "lodash";
This works because there's no "default" exported class. The difference in mine was I needed to find the way that was provided to load in 3rd party libraries: vendor.ts which sat at: 
src/vendor.ts
My vendor.ts file looks like this now:
import '@angular/platform-browser';
import '@angular/platform-browser-dynamic';
import '@angular/core';
import '@angular/common';
import '@angular/http';
import '@angular/router';
import 'rxjs';
import 'lodash';
// Other vendors for example jQuery, Lodash or Bootstrap
// You can import js, ts, css, sass, ...
Maybe it is too strange, but none of the above helped me, first of all, because I had properly installed the lodash (also re-installed via above suggestions).
So long story short the issue was connected with using _.has method from lodash.
I fixed it by simply using JS in operator.
You can also go ahead and import via good old require, ie:
const _get: any = require('lodash.get');
This is the only thing that worked for us. Of course, make sure any require() calls come after imports.
        
Thanks for contributing an answer to Stack Overflow!
Please be sure to answer the question. Provide details and share your research!
But avoid …
Asking for help, clarification, or responding to other answers.
Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.