When I have updated node to 5.1.0 and npm to 3.5.0 I cant generate gulp-angular app

[jwickowski]

npm ERR! Windows_NT 6.3.9600 npm ERR! argv "C:\Program Files\nodejs\node.exe" "C:\Users\jwickowski\AppD ata\Roaming\npm\node_modules\npm\bin\npm-cli.js" "install" npm ERR! node v5.1.0 npm ERR! npm v3.5.0 npm ERR! code ELIFECYCLE

npm ERR! deasync@0.1.1 install: node ./build.js npm ERR! Exit status 1 npm ERR! npm ERR! Failed at the deasync@0.1.1 install script 'node ./build.js'. npm ERR! Make sure you have the latest version of node.js and npm installed. npm ERR! If you do, this is most likely a problem with the deasync package, npm ERR! not with npm itself. npm ERR! Tell the author that this fails on your system: npm ERR! node ./build.js npm ERR! You can get their info via: npm ERR! npm owner ls deasync npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request: npm ERR! C:\x1\npm-debug.log

[jwickowski]

ERROR in Entry module not found: Error: Cannot resolve module 'awesome-typescrip t-loader' in ''

[anishbenji]

There seems to be issues with some of the dependencies of gulp-angular and npm 3. The same issue occurs when installing npm 3.x on earlier versions of Node.js as well. From what I understand npm 3 does some sort of de-duplication of dependencies of installed packages that causes some of them to fail. The packages need to updated to work with npm 3. Maybe someone with more experience on the matter can chime in.

[busches]

Please attach the yo-rc file. On Nov 29, 2015 10:57 AM, "Anish Benjamin" notifications@github.com wrote:

There seems to be issues with some of the dependencies of gulp-angular and npm 3. The same issue occurs when installing npm 3.x on earlier versions of Node.js as well. From what I understand npm 3 does some sort of de-duplication of dependencies of installed packages that causes some of them to fail. The packages need to updated to work with npm 3. Maybe someone with more experience on the matter can chime in.

— Reply to this email directly or view it on GitHub https://github.com/Swiip/generator-gulp-angular/issues/931#issuecomment-160431955 .

[Swiip]

I have npm 3 and it's working. Npm update implies a difficult migration for a lot of people but it should work. As @busches said, you can't just gives us error logs. We need your options, I don't even know at which point you have this errors? Installing the generator? Using it? Check the contributors doc.

[jwickowski]

i have tested other options. I have problem with the configuration which using TypeScript only

[Swiip]

Please put some effort in submitting, at least respond to direct questions. https://github.com/Swiip/generator-gulp-angular/blob/master/CONTRIBUTING.md

[ghost]

I am encountering the same issue. Installed using all default options except choosing Typescript :)

OS: Windows 10 x64 Node: v5.1.0 Npm: v3.5.0

Here is a copy of my yo-rc:

{
  "generator-gulp-angular": {
    "version": "1.0.2",
    "props": {
      "angularVersion": "~1.4.2",
      "angularModules": [
        {
          "key": "animate",
          "module": "ngAnimate"
        },
        {
          "key": "cookies",
          "module": "ngCookies"
        },
        {
          "key": "touch",
          "module": "ngTouch"
        },
        {
          "key": "sanitize",
          "module": "ngSanitize"
        },
        {
          "key": "messages",
          "module": "ngMessages"
        },
        {
          "key": "aria",
          "module": "ngAria"
        }
      ],
      "jQuery": {
        "key": "jquery2"
      },
      "resource": {
        "key": "angular-resource",
        "module": "ngResource"
      },
      "router": {
        "key": "ui-router",
        "module": "ui.router"
      },
      "ui": {
        "key": "bootstrap",
        "module": null
      },
      "bootstrapComponents": {
        "key": "ui-bootstrap",
        "module": "ui.bootstrap"
      },
      "cssPreprocessor": {
        "key": "node-sass",
        "extension": "scss"
      },
      "jsPreprocessor": {
        "key": "typescript",
        "extension": "ts",
        "srcExtension": "ts"
      },
      "htmlPreprocessor": {
        "key": "noHtmlPrepro",
        "extension": "html"
      },
      "foundationComponents": {
        "name": null,
        "version": null,
        "key": null,
        "module": null
      },
      "paths": {
        "src": "src",
        "dist": "dist",
        "e2e": "e2e",
        "tmp": ".tmp"
      }
    }
  }
}

I believe it is related to using "~0.14.0" of awesome-typescript-loader. (see https://github.com/s-panferov/awesome-typescript-loader/issues/68)

[ghost]

As a temporary work-around you can add a dependency on ts-loader:

1. npm install --save-dev ts-loader
2. On line 19 of scripts.js replace 'awesome-typescript-loader' with 'ts-loader'

[Swiip]

@jasteph Thanks for these elements. Looks like awesome-typescript-loader has some serious issues on Windows. I remember choosing this ts loader because it was the only one using TS 1.5 at the time but of course every ts loader has 1.5+ now. We should change loader.

[SalmonRiver]

If you use ts-loader there are some additional install steps found at https://github.com/TypeStrong/ts-loader

They worked for me.

[UzEE]

I'm also getting this issue when trying to setup a previously generated project on a new Windows 10 machine (while running npm install). It looks like the issue is definitely tied to npm v3.x.x since my old machine (running npm v2.x.x) is working fine.

[andrea-spotsoftware]

+1

@SalmonRiver could you please add some details about the replacing of awesome-typescript-loader with ts-loader?

Thank you so much.

[gelevanog]

same here with new version of node and npm Sorry... never mind ... the problem is not with the generating of app