Skip to content
This repository has been archived by the owner on Dec 1, 2019. It is now read-only.

'ERROR in Unexpected strict mode reserved word' on 0.15.0-rc.1 #76

Closed
TomaszScisloGS opened this issue Nov 18, 2015 · 13 comments
Closed

Comments

@TomaszScisloGS
Copy link

Hi,

I've got ERROR in Unexpected strict mode reserved word in verion 0.15.0-rc1

node: 0.10.36
OS: Windows 7 64bit

Is it something on my site?

Regards,
Tomasz Ścisło

@s-panferov
Copy link
Owner

@TomaszScisloGS v0.15.0 is unstable right now and works only at node v5.0.0. I'll fix this asap.

@s-panferov
Copy link
Owner

@TomaszScisloGS I've just published v0.15.0-rc.2, could you please try it? It might work on your node version.

@TomaszScisloGS
Copy link
Author

I will try with 0.15.2 and let you know ASAP, how about version 0.14.2?

@tscislo
Copy link

tscislo commented Nov 18, 2015

Unfortunately 0.15.0-rc.2 doesn't work with node 0.10.40. Any suggestions?

@s-panferov
Copy link
Owner

@tscislo v0.15.0 version finally works. Can you check?

@s-panferov
Copy link
Owner

@TomaszScisloGS please check v0.15.0

@TomaszScisloGS
Copy link
Author

With 0.15.0 and node 0.10.36 I get:

Unhandled rejection TypeError: Cannot call method 'getOptionsDiagnostics' of undefined
at Object.getPreEmitDiagnostics (h:\Projects\WDP\src\web\node_modules\typescript\lib\typescript.js:35386:35)
at Compiler. (h:\Projects\WDP\src\web\node_modules\awesome-typescript-loader\dist.babel\instance.js:261:40)
at Compiler.next (h:\Projects\WDP\src\web\node_modules\webpack-stream\node_modules\webpack\node_modules\tapable\lib\Tapable.js:69:14)
at Compiler. (h:\Projects\WDP\src\web\node_modules\webpack-stream\node_modules\webpack\lib\CachePlugin.js:40:4)
at Compiler.applyPluginsAsync (h:\Projects\WDP\src\web\node_modules\webpack-stream\node_modules\webpack\node_modules\tapable\lib\Tapable.js:71:13)
at Compiler. (h:\Projects\WDP\src\web\node_modules\webpack-stream\node_modules\webpack\lib\Compiler.js:400:9)
at Compilation. (h:\Projects\WDP\src\web\node_modules\webpack-stream\node_modules\webpack\lib\Compilation.js:576:13)
at Compilation.applyPluginsAsync (h:\Projects\WDP\src\web\node_modules\webpack-stream\node_modules\webpack\node_modules\tapable\lib\Tapable.js:60:69)
at Compilation. (h:\Projects\WDP\src\web\node_modules\webpack-stream\node_modules\webpack\lib\Compilation.js:571:10)
at Compilation.applyPluginsAsync (h:\Projects\WDP\src\web\node_modules\webpack-stream\node_modules\webpack\node_modules\tapable\lib\Tapable.js:60:69)
at Compilation. (h:\Projects\WDP\src\web\node_modules\webpack-stream\node_modules\webpack\lib\Compilation.js:566:9)
at Compilation.applyPluginsAsync (h:\Projects\WDP\src\web\node_modules\webpack-stream\node_modules\webpack\node_modules\tapable\lib\Tapable.js:60:69)
at Compilation. (h:\Projects\WDP\src\web\node_modules\webpack-stream\node_modules\webpack\lib\Compilation.js:562:8)
at Compilation.applyPluginsAsync (h:\Projects\WDP\src\web\node_modules\webpack-stream\node_modules\webpack\node_modules\tapable\lib\Tapable.js:60:69)
at Compilation.seal (h:\Projects\WDP\src\web\node_modules\webpack-stream\node_modules\webpack\lib\Compilation.js:524:7)
at Compiler. (h:\Projects\WDP\src\web\node_modules\webpack-stream\node_modules\webpack\lib\Compiler.js:397:15)
at h:\Projects\WDP\src\web\node_modules\webpack-stream\node_modules\webpack\node_modules\tapable\lib\Tapable.js:103:11
at Compilation. (h:\Projects\WDP\src\web\node_modules\webpack-stream\node_modules\webpack\lib\Compilation.js:444:10)
at Compilation.errorAndCallback (h:\Projects\WDP\src\web\node_modules\webpack-stream\node_modules\webpack\lib\Compilation.js:343:3)
at Compilation. (h:\Projects\WDP\src\web\node_modules\webpack-stream\node_modules\webpack\lib\Compilation.js:399:12)
at h:\Projects\WDP\src\web\node_modules\webpack-stream\node_modules\webpack\lib\Compilation.js:123:4
at Array.forEach (native)

@tscislo
Copy link

tscislo commented Nov 19, 2015

Doesn't work for me either.

@s-panferov
Copy link
Owner

I've finally found the error source. Please try version v0.15.1

@tscislo
Copy link

tscislo commented Nov 22, 2015

Unfortunately now I'm facing this issue: #77 and I cannot verify this one.

@s-panferov
Copy link
Owner

Issue was resolved by #79, landed as v0.15.2. Please try it.

@s-panferov
Copy link
Owner

@tscislo also please note, that default tsconfig which the generator generates is not good.

@tscislo
Copy link

tscislo commented Nov 28, 2015

With 0.15.2 it works as expected. Thanks @s-panferov ! Can be closed now

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants