{"action":"opened","issue":{"url":"https://api.github.com/repos/s-panferov/awesome-typescript-loader/issues/130","repository_url":"https://api.github.com/repos/s-panferov/awesome-typescript-loader","labels_url":"https://api.github.com/repos/s-panferov/awesome-typescript-loader/issues/130/labels{/name}","comments_url":"https://api.github.com/repos/s-panferov/awesome-typescript-loader/issues/130/comments","events_url":"https://api.github.com/repos/s-panferov/awesome-typescript-loader/issues/130/events","html_url":"https://github.com/s-panferov/awesome-typescript-loader/issues/130","id":151861845,"number":130,"title":"Error : Emit skipped followed by no Typescript error","user":{"login":"raybooysen","id":461957,"avatar_url":"https://avatars.githubusercontent.com/u/461957?v=3","gravatar_id":"","url":"https://api.github.com/users/raybooysen","html_url":"https://github.com/raybooysen","followers_url":"https://api.github.com/users/raybooysen/followers","following_url":"https://api.github.com/users/raybooysen/following{/other_user}","gists_url":"https://api.github.com/users/raybooysen/gists{/gist_id}","starred_url":"https://api.github.com/users/raybooysen/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/raybooysen/subscriptions","organizations_url":"https://api.github.com/users/raybooysen/orgs","repos_url":"https://api.github.com/users/raybooysen/repos","events_url":"https://api.github.com/users/raybooysen/events{/privacy}","received_events_url":"https://api.github.com/users/raybooysen/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2016-04-29T13:09:24Z","updated_at":"2016-04-29T13:09:24Z","closed_at":null,"body":"In some cases, and I can't figure out why, when we have a syntax error where Typescript cannot compile the code, the loader will output something like the stack trace below but not include the typescript error itself.  I then have to run Typescript: `tsc` and Typescript will show me the actual error.\r\n\r\nAny reason why the loader won't show the typescript error?\r\n\r\nTypescript output:\r\n```\r\nsrc/bootstrapping/shellBootstrapper.ts(58,31): error TS2339: Property 'createChild' does not exist on type 'Logger'.\r\n```\r\n\r\nTypescript Loader output:\r\n\r\n```\r\nError: Emit skipped Error: Emit skipped\r\nat State.emit (/home/ray/source/proj/node_modules/awesome-typescript-loader/dist.babel/host.js:291:23)\r\nat transform (/home/ray/source/proj/node_modules/awesome-typescript-loader/dist.babel/index.js:203:48)\r\nat _callee3$ (/home/ray/source/proj/node_modules/awesome-typescript-loader/dist.babel/index.js:258:42)\r\nat tryCatch (/home/ray/source/proj/node_modules/babel-regenerator-runtime/runtime.js:61:40)\r\nat GeneratorFunctionPrototype.invoke [as _invoke] (/home/ray/source/proj/node_modules/babel-regenerator-runtime/runtime.js:329:22)\r\nat GeneratorFunctionPrototype.prototype.(anonymous function) [as next] (/home/ray/source/proj/node_modules/babel-regenerator-runtime/runtime.js:94:21)\r\nat fulfilled (/home/ray/source/proj/node_modules/awesome-typescript-loader/dist.babel/index.js:31:32)\r\nat run (/home/ray/source/proj/node_modules/core-js/modules/es6.promise.js:89:22)\r\nat /home/ray/source/proj/node_modules/core-js/modules/es6.promise.js:102:28\r\nat flush (/home/ray/source/proj/node_modules/core-js/modules/_microtask.js:18:9)\r\nat _combinedTickCallback (internal/process/next_tick.js:67:7)\r\nat process._tickCallback (internal/process/next_tick.js:98:9)\r\nModuleBuildError: Module build failed: Error: Emit skipped\r\nat State.emit (/home/ray/source/proj/node_modules/awesome-typescript-loader/dist.babel/host.js:291:23)\r\nat transform (/home/ray/source/proj/node_modules/awesome-typescript-loader/dist.babel/index.js:203:48)\r\nat _callee3$ (/home/ray/source/proj/node_modules/awesome-typescript-loader/dist.babel/index.js:258:42)\r\nat tryCatch (/home/ray/source/proj/node_modules/babel-regenerator-runtime/runtime.js:61:40)\r\nat GeneratorFunctionPrototype.invoke [as _invoke] (/home/ray/source/proj/node_modules/babel-regenerator-runtime/runtime.js:329:22)\r\nat GeneratorFunctionPrototype.prototype.(anonymous function) [as next] (/home/ray/source/proj/node_modules/babel-regenerator-runtime/runtime.js:94:21)\r\nat fulfilled (/home/ray/source/proj/node_modules/awesome-typescript-loader/dist.babel/index.js:31:32)\r\nat run (/home/ray/source/proj/node_modules/core-js/modules/es6.promise.js:89:22)\r\nat /home/ray/source/proj/node_modules/core-js/modules/es6.promise.js:102:28\r\nat flush (/home/ray/source/proj/node_modules/core-js/modules/_microtask.js:18:9)\r\nat _combinedTickCallback (internal/process/next_tick.js:67:7)\r\nat process._tickCallback (internal/process/next_tick.js:98:9)\r\nat DependenciesBlock.onModuleBuildFailed (/home/ray/source/proj/node_modules/webpack-core/lib/NormalModuleMixin.js:315:19)\r\nat nextLoader (/home/ray/source/proj/node_modules/webpack-core/lib/NormalModuleMixin.js:270:31)\r\nat /home/ray/source/proj/node_modules/webpack-core/lib/NormalModuleMixin.js:292:15\r\nat context.callback (/home/ray/source/proj/node_modules/webpack-core/lib/NormalModuleMixin.js:148:14)\r\nat _callee3$ (/home/ray/source/proj/node_modules/awesome-typescript-loader/dist.babel/index.js:285:25)\r\nat tryCatch (/home/ray/source/proj/node_modules/babel-regenerator-runtime/runtime.js:61:40)\r\nat GeneratorFunctionPrototype.invoke [as _invoke] (/home/ray/source/proj/node_modules/babel-regenerator-runtime/runtime.js:329:22)\r\nat GeneratorFunctionPrototype.prototype.(anonymous function) [as next] (/home/ray/source/proj/node_modules/babel-regenerator-runtime/runtime.js:94:21)\r\nat fulfilled (/home/ray/source/proj/node_modules/awesome-typescript-loader/dist.babel/index.js:31:32)\r\nat run (/home/ray/source/proj/node_modules/core-js/modules/es6.promise.js:89:22)\r\nat /home/ray/source/proj/node_modules/core-js/modules/es6.promise.js:102:28\r\nat flush (/home/ray/source/proj/node_modules/core-js/modules/_microtask.js:18:9)\r\nat _combinedTickCallback (internal/process/next_tick.js:67:7)\r\nat process._tickCallback (internal/process/next_tick.js:98:9)\r\n./no\r\nnpm ERR! Linux 4.4.0-21-generic\r\nnpm ERR! argv \"/usr/bin/nodejs\" \"/usr/bin/npm\" \"run\" \"build-dev\"\r\nnpm ERR! node v5.11.0\r\nnpm ERR! npm  v3.8.6\r\nnpm ERR! code ELIFECYCLE\r\nnpm ERR! proj@1.0.0 build-dev: `set NODE_ENV=dev&& webpack --bail --display-reasons --display-error-details`\r\nnpm ERR! Exit status 1\r\nnpm ERR!\r\n    npm ERR! Failed at the proj@1.0.0 build-dev script 'set NODE_ENV=dev&& webpack --bail --display-reasons --display-error-details'.\r\n    npm ERR! Make sure you have the latest version of node.js and npm installed.\r\n    npm ERR! If you do, this is most likely a problem with the proj package,\r\n    npm ERR! not with npm itself.\r\n    npm ERR! Tell the author that this fails on your system:\r\n    npm ERR!     set NODE_ENV=dev&& webpack --bail --display-reasons --display-error-details\r\nnpm ERR! You can get information on how to open an issue for this project with:\r\nnpm ERR!     npm bugs proj\r\nnpm ERR! Or if that isn't available, you can get their info via:\r\nnpm ERR!     npm owner ls proj\r\nnpm ERR! There is likely additional logging output above.\r\n```\r\n\r\n"}}