You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
node --versionv10.0.0npm --version6.0.1nvm --version0.33.11npm run build
> angular2-token@0.2.0-beta.14 build /home/user/node_modules/angular2-token
> rimraf dist && ng-packagr -p ng-package.jsonBuilding Angular PackageBuilding entry point 'angular2-token'Cleaning build directoryRendering StylesheetsRendering TemplatesCompiling TypeScript sources through ngcBundling to FESM15BUILD ERRORCould not resolve './a2t-ui/a2t-ui.module' from .ng_pkg_build/angular2-token/out/public_api.jsError: Could not resolve './a2t-ui/a2t-ui.module' from .ng_pkg_build/angular2-token/out/public_api.js at error (/home/user/node_modules/angular2-token/node_modules/rollup/dist/rollup.js:170:15) at /home/user/node_modules/angular2-token/node_modules/rollup/dist/rollup.js:19580:25
test
npm test
> angular2-token@0.2.0-beta.14 test /home/user/node_modules/angular2-token
> karma startSTART:(node:11200) DeprecationWarning: Tapable.plugin is deprecated. Use new API on `.hooks` instead⚠ 「wdm」: ℹ 「wdm」: Compiled with warnings.ℹ 「wdm」: Compiling...[at-loader] Using typescript@2.7.2 from typescript and "tsconfig.json" from /home/user/node_modules/angular2-token/tsconfig.json.[at-loader] Checking started in a separate process...[at-loader] Ok, 1.192 sec.⚠ 「wdm」: ℹ 「wdm」: Compiled with warnings.18 05 2018 23:12:12.543:INFO [karma]: Karma v2.0.2 server started at http://0.0.0.0:9876/18 05 2018 23:12:12.545:INFO [launcher]: Launching browser Chrome with unlimited concurrency18 05 2018 23:12:12.633:INFO [launcher]: Starting browser Chromeℹ 「wdm」: Compiling...[at-loader] Checking started in a separate process...[at-loader] Ok, 0.004 sec.⚠ 「wdm」: ℹ 「wdm」: Compiled with warnings.ℹ 「wdm」: Compiling...18 05 2018 23:12:40.588:INFO [Chrome 66.0.3359 (Linux 0.0.0)]: Connected on socket qfKp6xrqQFsqXnULAAAB with id 23799729 Angular2TokenService ✔ validateToken should call signOut when it returns status 401 ✔ validateToken should not call signOut when it returns status 401 ✔ Methods should send to configured path ✔ signOut method should clear local storage ✔ signIn method should receive headers and set local storage18 05 2018 23:12:58.115:WARN [Chrome 66.0.3359 (Linux 0.0.0)]: Disconnected (1 times), because no message in 10000 ms.Chrome 66.0.3359 (Linux 0.0.0) ERROR Disconnected, because no message in 10000 ms.Chrome 66.0.3359 (Linux 0.0.0) ERROR Disconnected, because no message in 10000 ms.Finished in 15.373 secs / 0.192 secs @ 23:12:58 GMT+0300 (MSK)=============================== Coverage summary ===============================Statements : 100% ( 0/0 )Branches : 100% ( 0/0 )Functions : 100% ( 0/0 )Lines : 100% ( 0/0 )================================================================================[at-loader] Checking started in a separate process...[at-loader] Ok, 0.004 sec.18 05 2018 23:13:05.733:WARN [launcher]: Chrome was not killed in 2000 ms, sending SIGKILL.npm ERR! Test failed. See above for more details.
The text was updated successfully, but these errors were encountered:
npm run build
> angular2-token@0.2.0 build /node_modules/angular2-token
> rimraf dist && ng-packagr -p ng-package.jsonBuilding Angular PackageBuilding entry point 'angular2-token'Rendering StylesheetsRendering TemplatesCompiling TypeScript sources through ngcBundling to FESM2015BUILD ERRORCould not resolve './a2t-ui/a2t-ui.component' from dist/esm2015/angular2-token.jsError: Could not resolve './a2t-ui/a2t-ui.component' from dist/esm2015/angular2-token.js at error (/node_modules/angular2-token/node_modules/rollup/dist/rollup.js:199:15) at /node_modules/angular2-token/node_modules/rollup/dist/rollup.js:20784:25npm ERR! code ELIFECYCLEnpm ERR! errno 111npm ERR! angular2-token@0.2.0 build: `rimraf dist && ng-packagr -p ng-package.json`npm ERR! Exit status 111npm ERR! npm ERR! Failed at the angular2-token@0.2.0 build script.npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
build
test
The text was updated successfully, but these errors were encountered: