[dba-Tech] Bad karma - a kind of punning, but not only - I have got an issue with nodejs' karma module while installing gulp...

[Salakhetdinov Shamil]

 Hi Jim --

The error messages I've got are coming (AFAIU) from

gulp-typescript - "A typescript compiler for gulp with incremental compilation support."
https://www.npmjs.com/package/gulp-typescript
installed on my MS Windows 8.1 globally as an npm module under:

C:\Users\{user name}\AppData\Roaming\npm\node_modules\gulp-typescript\node_modules\typescript\bin\tsc
C:\Users\(user name)\AppData\Roaming\npm\node_modules\gulp-typescript\node_modules\typescript\bin\tsc.js

And I'musing this gulp-typescript (again AFAIU - I have just started to work with TypeScript yesterday) to translate MS TypeScript compiler ready(?) sources:

1st:  TypeScript Sample: Todo MVC
https://github.com/Microsoft/TypeScriptSamples/tree/master/todomvc

2nd:   Modularization in TypeScript
https://keyholesoftware.com/2013/01/14/modularization-in-typescript/

Obviously(?) there should be incompatibility issues, which I have solved/I have tried to solve by editing the sources.
As far as I see I have solved most of them. A couple still exist but I hope to get them solved sooner or later.

I have also MS TypeScript v.1.0 compiler located under

C:\Program Files (x86)\Microsoft SDKs\TypeScript\1.0\tsc.exe
C:\Program Files (x86)\Microsoft SDKs\TypeScript\1.0\tsc.js
When I'm using it with the 1st (manually edited/adapted) sample's .ts sources, it compiles well.
When I'm using it with the 2nd (manually edited/adapted) sample's sources I'm getting the same compile-time error as with gulp-typescript

 error TS1005: ';' expected.

I wanted to avoid dependence of the latest TypeScript compiler version bundled with latest Visual Studio version, so I have started to use gulp-typescript. AFAIU and AFAUCS this approach creates some issues. The best for me probably (as I'm working  on MS Windows) should be to "merge" Sublime + gulp TypeScript development support and (the latest?) MS TypeScript compiler. There are several under:

"TypeScript 1.4 for Visual Studio 2013" 
https://visualstudiogallery.msdn.microsoft.com/2d42d8dc-e085-45eb-a30b-3f7d50d55304
And the last one will not be installed to run by default via MS Windows PATH search:

"tsc.exe should point to latest tsc after installing out of band installers #2068"
https://github.com/Microsoft/TypeScript/issues/2068 Outside of gulp/within VS 2012, I'm currently using tsc.exe v.1.0, which (AFAICG) I have got for my VS 2012 by installing

"TypeScript 1.0 Tools for Visual Studio 2012" 
https://visualstudiogallery.msdn.microsoft.com/fa041d2d-5d77-494b-b0ba-8b4550792b4d

AFAIS there is a new TypeScript development support version for VS2012, but even newer one for VS 2013 and the best (?) beta one v.1.5 for VS2015.

As it often happens with Microsoft they seems to be creating a "versions hell" based on "good intentions" of promoting the latest features of TypeScript and in the same time pushing forward VS upgrades.

...

But as I have noted previously I wanted to have my TypeScript learning/development independent from Visual Studio (versions) and target OS: this approach promise to force me to go through a few "hell circles" before I'll get my (gulp-)TypeScript development environment up & running smoothly. It may even happen I'll "surrender", I''l purchase VS2015/install VS 2015 community edition and I'll abandon gulp-typescript...

Thank you.

-- Shamil



Tuesday, June  2, 2015 7:24 PM -06:00 from Jim Lawrence <accessd at shaw.ca>:
>Hi Shamil:
>
>You are having so many problems...what system are you installing and compiling these application on, if you don't mind me asking?
>
>Is there any inherent issues with using pure JavaScript libraries (JQuery and NodeJS), for example, with TypeScript code?
>
>Jim
<<< skipped>>>
>