{"action":"created","issue":{"url":"https://api.github.com/repos/aurelia/skeleton-navigation/issues/628","repository_url":"https://api.github.com/repos/aurelia/skeleton-navigation","labels_url":"https://api.github.com/repos/aurelia/skeleton-navigation/issues/628/labels{/name}","comments_url":"https://api.github.com/repos/aurelia/skeleton-navigation/issues/628/comments","events_url":"https://api.github.com/repos/aurelia/skeleton-navigation/issues/628/events","html_url":"https://github.com/aurelia/skeleton-navigation/issues/628","id":167994855,"number":628,"title":"Build errors in typescript-webpack project when running build:dev","user":{"login":"don-bluelinegrid","id":19780097,"avatar_url":"https://avatars.githubusercontent.com/u/19780097?v=3","gravatar_id":"","url":"https://api.github.com/users/don-bluelinegrid","html_url":"https://github.com/don-bluelinegrid","followers_url":"https://api.github.com/users/don-bluelinegrid/followers","following_url":"https://api.github.com/users/don-bluelinegrid/following{/other_user}","gists_url":"https://api.github.com/users/don-bluelinegrid/gists{/gist_id}","starred_url":"https://api.github.com/users/don-bluelinegrid/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/don-bluelinegrid/subscriptions","organizations_url":"https://api.github.com/users/don-bluelinegrid/orgs","repos_url":"https://api.github.com/users/don-bluelinegrid/repos","events_url":"https://api.github.com/users/don-bluelinegrid/events{/privacy}","received_events_url":"https://api.github.com/users/don-bluelinegrid/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/aurelia/skeleton-navigation/labels/question","name":"question","color":"cc317c"}],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":18,"created_at":"2016-07-28T01:42:53Z","updated_at":"2016-10-12T21:24:53Z","closed_at":null,"body":"Running the skeleton-navigation/typescript-webpack project, I'm seeing these errors from the 'build:dev' task -\r\n-----\r\n`npm ERR! Darwin 15.5.0\r\nnpm ERR! argv \"/usr/local/bin/node\" \"/usr/local/bin/npm\" \"run\" \"webpack\" \"--\" \"--progress\" \"--profile\"\r\nnpm ERR! node v4.4.7\r\nnpm ERR! npm  v3.10.3\r\nnpm ERR! code ELIFECYCLE\r\nnpm ERR! aurelia-skeleton-navigation-webpack@1.0.0-beta.3.0.1 webpack: `cross-env ./node_modules/.bin/webpack \"--progress\" \"--profile\"`\r\nnpm ERR! Exit status 2\r\nnpm ERR! \r\nnpm ERR! Failed at the aurelia-skeleton-navigation-webpack@1.0.0-beta.3.0.1 webpack script 'cross-env ./node_modules/.bin/webpack \"--progress\" \"--profile\"'.\r\nnpm ERR! Make sure you have the latest version of node.js and npm installed.\r\nnpm ERR! If you do, this is most likely a problem with the aurelia-skeleton-navigation-webpack package,\r\nnpm ERR! not with npm itself.\r\nnpm ERR! Tell the author that this fails on your system:\r\nnpm ERR!     cross-env ./node_modules/.bin/webpack \"--progress\" \"--profile\"\r\nnpm ERR! You can get information on how to open an issue for this project with:\r\nnpm ERR!     npm bugs aurelia-skeleton-navigation-webpack\r\nnpm ERR! Or if that isn't available, you can get their info via:\r\nnpm ERR!     npm owner ls aurelia-skeleton-navigation-webpack\r\nnpm ERR! There is likely additional logging output above.\r\n\r\nnpm ERR! Please include the following file with any support request:\r\nnpm ERR!     /Users/.../Documents/gc-2/npm-debug.log\r\n\r\nnpm ERR! Darwin 15.5.0\r\nnpm ERR! argv \"/usr/local/bin/node\" \"/usr/local/bin/npm\" \"run\" \"build:dev\"\r\nnpm ERR! node v4.4.7\r\nnpm ERR! npm  v3.10.3\r\nnpm ERR! code ELIFECYCLE\r\nnpm ERR! aurelia-skeleton-navigation-webpack@1.0.0-beta.3.0.1 build:dev: `cross-env NODE_ENV=development npm run webpack -- --progress --profile`\r\nnpm ERR! Exit status 1\r\nnpm ERR! \r\nnpm ERR! Failed at the aurelia-skeleton-navigation-webpack@1.0.0-beta.3.0.1 build:dev script 'cross-env NODE_ENV=development npm run webpack -- --progress --profile'.\r\nnpm ERR! Make sure you have the latest version of node.js and npm installed.\r\nnpm ERR! If you do, this is most likely a problem with the aurelia-skeleton-navigation-webpack package,\r\nnpm ERR! not with npm itself.\r\nnpm ERR! Tell the author that this fails on your system:\r\nnpm ERR!     cross-env NODE_ENV=development npm run webpack -- --progress --profile\r\nnpm ERR! You can get information on how to open an issue for this project with:\r\nnpm ERR!     npm bugs aurelia-skeleton-navigation-webpack\r\nnpm ERR! Or if that isn't available, you can get their info via:\r\nnpm ERR!     npm owner ls aurelia-skeleton-navigation-webpack\r\nnpm ERR! There is likely additional logging output above.\r\n\r\nnpm ERR! Please include the following file with any support request:\r\nnpm ERR!     /Users/.../Documents/gc-2/npm-debug.log`\r\n-----\r\nI've attached the debug log, although it doesn't look too informative.\r\n\r\nAlso, as a side question -\r\nIf an application developer is building an application that was based on a skeleton project - like the typescript-webpack skeleton - what is the expected development process for incorporating changes made to the skeleton project?  \r\n\r\nI've tried to do this once with the recent beta.3.0.1 version, and all I could come up with was running diff on the entire folder structure and manually merging changes.  Since the app developer is not doing a Git checkout of the project, there isn't a Git merge that can be done, correct?\r\n\r\nRegards,\r\nDon\r\n[npm-debug.log.txt](https://github.com/aurelia/skeleton-navigation/files/387518/npm-debug.log.txt)\r\n\r\n\r\n"},"comment":{"url":"https://api.github.com/repos/aurelia/skeleton-navigation/issues/comments/253344114","html_url":"https://github.com/aurelia/skeleton-navigation/issues/628#issuecomment-253344114","issue_url":"https://api.github.com/repos/aurelia/skeleton-navigation/issues/628","id":253344114,"user":{"login":"Ixonal","id":1368543,"avatar_url":"https://avatars.githubusercontent.com/u/1368543?v=3","gravatar_id":"","url":"https://api.github.com/users/Ixonal","html_url":"https://github.com/Ixonal","followers_url":"https://api.github.com/users/Ixonal/followers","following_url":"https://api.github.com/users/Ixonal/following{/other_user}","gists_url":"https://api.github.com/users/Ixonal/gists{/gist_id}","starred_url":"https://api.github.com/users/Ixonal/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/Ixonal/subscriptions","organizations_url":"https://api.github.com/users/Ixonal/orgs","repos_url":"https://api.github.com/users/Ixonal/repos","events_url":"https://api.github.com/users/Ixonal/events{/privacy}","received_events_url":"https://api.github.com/users/Ixonal/received_events","type":"User","site_admin":false},"created_at":"2016-10-12T21:24:53Z","updated_at":"2016-10-12T21:24:53Z","body":"@EisenbergEffect I've been having this issue (using version 1.0.2 of the nav skeleton), but I think I found the problem, at least in my case. While builds were failing, when running the dev server, TypeScript was complaining about the aurelia-protractor custom typings. It complained that it couldn't find the Locator type and that the declaration of ProtractorBy in the actual protractor package was conflicting with the one in the custom typings. When I comment out everything in aurelia-protractor.d.ts, both the build and the run work properly. Not really a permanent solution, but does shed light on what's wrong."}}
{"actor":{"display_login":"Ixonal"}}