cannot build project from a fresh clone (no adjustments made by me
See original GitHub issueI’m submitting a … (check one with “x”)
[ ] Regression (a behavior that used to work and stopped working in a new release)
[X] Bug report <!-- Please check the repository for a similar issue or PR before submitting -->
[ ] Support request => <!-- Please check the repository for a similar issue or PR before submitting -->
[ ] Feature request
[ ] Documentation issue or request
Current behavior
I cannot get a build to work on windows. It always fails
Expected/desired behavior
Build correctly
Minimal reproduction of the problem with instructions
git clone https://github.com/ng-seed/universal.git test
cd test
yarn
npm run build:spa-dev
D:\Development\xxx\test>npm run build:spa-dev
> @ng-seed/universal@6.0.0 build:spa-dev D:\Development\xxx\test
> npm run clean:artifacts && gulp build:spa-dev --color
> @ng-seed/universal@6.0.0 clean:artifacts D:\Development\xxx\test
> rimraf .cache .server/server* .temp public
[17:41:05] Using gulpfile D:\Development\xxx\test\gulpfile.js
[17:41:05] Starting 'build:spa-dev'...
[17:41:05] Starting 'bundle:spa-dev'...
DLL: Checking if DLLs are valid.
DLL: Rebuilding...
DLL: Bundling done, all DLLs are valid.
[hard-source:core] HardSourceWebpackPlugin is writing to a new confighash path for the first time: D:\Development\xxx\test\node_modules\.cache\hard-source\54ff588682b2a3f4e44ba5e957357f6ecca7d50ba475dcfa9a26a70d170b0e0a
[at-loader] Using typescript@2.6.2 from typescript and "tsconfig.json" from D:\Development\xxx\test/tsconfig.json.
================================== ng-router-loader ==================================
Importer: D:\Development\xxx\test\src\client\app\app.routes.ts
Raw Request: ./components/+home/home.module#HomeModule
Replacement: function() { return new Promise(function (resolve) { require.ensure([], function (require) { resolve(require('D:\\Development\\xxx\\test\\src\\client\\app\\components\\+home\\home.module')['HomeModule']); });})}
======================================================================================
================================== ng-router-loader ==================================
Importer: D:\Development\xxx\test\src\client\app\app.routes.ts
Raw Request: ./components/+about/about.module#AboutModule
Replacement: function() { return new Promise(function (resolve) { require.ensure([], function (require) { resolve(require('D:\\Development\\xxx\\test\\src\\client\\app\\components\\+about\\about.module')['AboutModule']); });})}
======================================================================================
================================== ng-router-loader ==================================
Importer: D:\Development\xxx\test\src\client\app\app.routes.ts
Raw Request: ./components/+secure/secure.module#SecureModule
Replacement: function() { return new Promise(function (resolve) { require.ensure([], function (require) { resolve(require('D:\\Development\\xxx\\test\\src\\client\\app\\components\\+secure\\secure.module')['SecureModule']); });})}
======================================================================================
(node:2368) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 1): Error: callback(): The callback was already called.
(node:2368) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
[17:41:28] The following tasks did not complete: build:spa-dev, bundle:spa-dev
[17:41:28] Did you forget to signal async completion?
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! @ng-seed/universal@6.0.0 build:spa-dev: `npm run clean:artifacts && gulp build:spa-dev --color`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the @ng-seed/universal@6.0.0 build:spa-dev script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\chris\AppData\Roaming\npm-cache\_logs\2018-02-28T22_41_28_656Z-debug.log
What is the motivation / use case for changing the behavior?
Building the project
Environment
- Angular version: 6.0.0-beta.0
- Browser:
- Chrome (desktop) version XX
- Chrome (Android) version XX
- Chrome (iOS) version XX
- Firefox version XX
- Safari (desktop) version XX
- Safari (iOS) version XX
- IE version XX
- Edge version XX
- For Tooling issues:
- Node version: 8.9.4
- Platform: Windows 10
- Others:
I am sure I am missing something, but i’m following the steps exactly from a blank slate and cannot get it to build, maybe I am missing some global dependencies?
Not sure why a fresh clone, yarn, and build would fail as I have modified nothing in the files from the clone
Issue Analytics
- State:
- Created 6 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Unable to build solution after cloning the repo #24270 - GitHub
The build failed, so used command line build.cmd to build the project. I am getting this error: .\build.cmd "C:\AspNetCoreSrcCode\src\Mvc\Mvc.
Read more >Cannot build or upload project after cloning from Github? - clion
To change them, click it and go to 'edit configurations'. A new prompt window will open. On the left hand toolbar labeled 'Templates',...
Read more >Files showing as modified directly after a Git clone
The solution was to rename foo.py to an entirely different file name that in no way conflicted with the original. The problem went...
Read more >git - Can't clone remote repository - Visual Studio Feedback
I found a workaround. It turns out that for some (but not all) installations the RC installer is installing a prerelease version of...
Read more >Cannot set interpreter on project cloned from git. : PY-49397
In fact, the project does not show up by name in the settings as it normally would. If I create a new Django...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I also get the exact same error on my Mac, really hope someone can tell me what I am doing wrong
Mac is running node 8.8.1 and npm 5.6.0
@chrisworrell thanks too, your attention to this detail saved the project 👍