Build angular-cli fork fails

[fuitattila]

Please provide us with the following information:

OS?

Windows 10.

Versions.

angular-cli: 1.0.0-beta.26
node: 5.11.0
os: win32 ia32
@angular/compiler: 2.4.5
@angular/compiler-cli: 2.4.5
@angular/core: 2.4.5
@angular/tsc-wrapped: 0.5.1

Repro steps.

1. I have downloaded beta26 angular-cli, from here: https://github.com/angular/angular-cli/releases/tag/v1.0.0-beta.26
2. npm install - success
3. npm run build - fails

The log given by the failure.

node ./scripts/publish/build.js

Deleting dist folder...
Creating schema.d.ts...
module.js:341
    throw err;
    ^

Error: Cannot find module 'C:\Users\Fuit'
    at Function.Module._resolveFilename (module.js:339:15)
    at Function.Module._load (module.js:290:25)
    at Function.Module.runMain (module.js:447:10)
    at startup (node.js:148:18)
    at node.js:405:3
Command failed: node C:\Users\Fuit Attila\Desktop\angular-cli-1.0.0-beta.26\scripts\build-schema-dts.js C:\Users\Fuit At
tila\Desktop\angular-cli-1.0.0-beta.26\packages\angular-cli\lib\config\schema.json C:\Users\Fuit Attila\Desktop\angular-
cli-1.0.0-beta.26\packages\angular-cli\lib\config\schema.d.ts
module.js:341
    throw err;
    ^

Error: Cannot find module 'C:\Users\Fuit'
    at Function.Module._resolveFilename (module.js:339:15)
    at Function.Module._load (module.js:290:25)
    at Function.Module.runMain (module.js:447:10)
    at startup (node.js:148:18)
    at node.js:405:3


npm ERR! Windows_NT 10.0.14393
npm ERR! argv "C:\\Program Files (x86)\\nodejs\\node.exe" "C:\\Program Files (x86)\\nodejs\\node_modules\\npm\\bin\\npm-
cli.js" "run" "build"
npm ERR! node v5.11.0
npm ERR! npm  v3.8.6
npm ERR! code ELIFECYCLE
npm ERR! [email protected] build: node ./scripts/publish/build.js
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] build script 'node ./scripts/publish/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 angular-cli package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node ./scripts/publish/build.js
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs angular-cli
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls angular-cli
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     C:\Users\Fuit Attila\Desktop\angular-cli-1.0.0-beta.26\npm-debug.log
PS C:\Users\Fuit Attila\Desktop\angular-cli-1.0.0-beta.26

---

What am I doing wrong?

Thank you for your help!

[catull]

@fuitattila
Going out on a limb, could you rename the folder "C:\Users\Fuit_Attila\Desktop\angular-cli-1.0.0-beta.26" or "...\FuitAttila..." and re-try ? Or move it to c:\temp and try from there.

[fuitattila]

@catull
Good idea thank you! I will give it a try soon.

[fuitattila]

@catull
I have moved my project to here: C:\WORK.... It worked, thank you!

But now I have an other failure:

> [email protected] build C:\WORK\angular-cli-1.0.0-beta.26
> node ./scripts/publish/build.js

Deleting dist folder...
Creating schema.d.ts...
Compiling packages...
  @angular-cli\ast-tools
Compilation error.
node_modules/@types/lodash/index.d.ts(245,25): error TS2304: Cannot find name 'Partial'.

Any idea what am I doing wrong? Maybe I shoud install some typings globally - unit it will be fixed?

[fuitattila]

In package.json should upgrade typescript version:

"typescript": "~2.1.0"

Than it builds perfectly! I hope it helps to build an own fork from beta26 :/

@filipesilva is this a bug?

[catull]

This issue can be closed now.
The solution is to not have a path with a space in it.

@fuitattila The next issue you reported has nothing to do with your original issue. Please open a new separate one.

[filipesilva]

@fuitattila not being able to build on windows when on a path with spaces is a bug.

The cannot find name partial bug was fixed with #4260.

[angular-automatic-lock-bot]

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}