Hi Sander,

Thank you for your help and advice. I really appreciate it.

Yeah. It is true what you say, that you need to puzzle around with the 3rth 
party libs, as not all version work with all versions – and this is to me 
(beginner) the most discouraging thing to learn about NodeJS/npm and 
Angular. I am just starting to learn about all those technologies. The only 
reason I have tried to convert “angular2byexample-base\trainer” to the 
latest packages was that running “npm install“ on the original code for the 
“angular2byexample-base\training” project is generating those warnings:


c:\tmp\Experiment4\angular2byexample-base\trainer>npm install
> npm WARN registry Unexpected warning for https://registry.npmjs.org/: 
> Miscellaneous Warning TETIMEDOUT: request to 
> https://registry.npmjs.org/gulp failed, reason: connec
> TIMEDOUT 104.16.27.35:443
> npm WARN registry Using stale package data from 
> https://registry.npmjs.org/ due to a request error during revalidation.
> npm WARN deprecated [email protected]: gulp-util is deprecated - replace it, 
> following the guidelines at https://medium.com/gulpjs/gulp-util-ca3b1f9f9ac5
> npm WARN deprecated [email protected]: connect 2.x series is deprecated
> npm WARN deprecated [email protected]: Use the built-in module in node 9.0.0 or 
> newer, instead
> npm WARN deprecated [email protected]: gulp-util is deprecated - replace 
> it, following the guidelines at 
> https://medium.com/gulpjs/gulp-util-ca3b1f9f9ac5
> npm WARN deprecated [email protected]: please upgrade to graceful-fs 4 
> for compatibility with current and future versions of Node.js
> npm WARN deprecated [email protected]: Please update to minimatch 3.0.2 or 
> higher to avoid a RegExp DoS issue
> npm WARN deprecated [email protected]: Please update to minimatch 3.0.2 or 
> higher to avoid a RegExp DoS issue
> npm WARN deprecated [email protected]: please upgrade to graceful-fs 4 for 
> compatibility with current and future versions of Node.js
> npm notice created a lockfile as package-lock.json. You should commit this 
> file.
> npm WARN [email protected] No license field.
> npm WARN optional SKIPPING OPTIONAL DEPENDENCY: [email protected] 
> (node_modules\fsevents):
> npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for 
> [email protected]: wanted {"os":"darwin","arch":"any"} (current: 
> {"os":"win32","arch":"x64"})

 

But at least the code is running when I execute command “gulp play” (again 
with some warnings):


C:\tmp\Experiment4\angular2byexample-base\trainer>gulp play
> [11:27:42] Using gulpfile 
> C:\tmp\Experiment4\angular2byexample-base\trainer\gulpfile.js
> (node:10168) ExperimentalWarning: The http2 module is an experimental API.
> [11:27:42] Starting 'ts2js'...
> C:/tmp/Experiment4/angular2byexample-base/trainer/node_modules/@types/core-js/index.d.ts(21,14):
>  
> error TS2300: Duplicate identifier 'PropertyKey'.
> C:/tmp/Experiment4/angular2byexample-base/trainer/node_modules/rxjs/Subject.d.ts(24,5):
>  
> error TS2416: Property 'lift' in type 'Subject<T>' is not assignable to the 
> same p
> roperty in base type 'Observable<T>'.
>   Type '<T, R>(operator: Operator<T, R>) => Observable<T>' is not 
> assignable to type '<R>(operator: Operator<T, R>) => Observable<R>'.
>     Type 'Observable<T>' is not assignable to type 'Observable<R>'.
>       Type 'T' is not assignable to type 'R'.
> C:/tmp/Experiment4/angular2byexample-base/trainer/node_modules/typescript/lib/lib.d.ts(105,14):
>  
> error TS2300: Duplicate identifier 'PropertyKey'.
> [11:27:46] TypeScript: 3 semantic errors
> [11:27:46] TypeScript: emit succeeded (with errors)
> [11:27:46] Finished 'ts2js' after 3.88 s
> [11:27:46] Starting 'play'...
> [11:27:46] Finished 'play' after 349 ms
> [11:27:46] Server started http://localhost:9000
> [11:27:46] LiveReload started on port 35729


So there is no really some kind of procedure that would allow developer to 
find out precisely which version of dependent packages developer should be 
using?

Regards,

Janusz



On Saturday, 4 August 2018 16:19:20 UTC+10, Sander Elias wrote:
>
> Hmm, ok,
>
> Perhaps you should give the original versions a try first. If you are 
> starting, there isn't a difference in version. New versions add stuff, but 
> seldom change things. and the things that are changed are not in a beginner 
> course.. (check the changelog if you want, the upgrade guide 
> <https://update.angular.io/>)
>
> upgrading an existing app isn't hard, but sometimes you need to puzzle 
> around with the 3rth party libs, as not all version work with all versions. 
> But that is outside of the scope of learning angular.
>
> Regards
> Sander
>

-- 
You received this message because you are subscribed to the Google Groups 
"Angular and AngularJS discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/angular.
For more options, visit https://groups.google.com/d/optout.

Reply via email to