Latest version of Angular?

Hi all

What is the latest version of Angular? I need to build a tic tac toe game.

Thanks

I guess the best source for this type of information is https://angularjs.org/

1 Like

The latest version of Angular is Angular 8.

FYI, that website is for the original first version of Angular (1.x). The current 2.x+ version of Angular has a different website: https://angular.io/

2 Likes

You’re right. The user that accesses angularjs.org and clicks in the “Try the New Angular” button is redirected to angularjs.io .

To be clear there are 2 distinct versions of “Angular”

  1. AngularJs - latest is version 1.7.8, which is the legacy version of the framework that is in LTS. If your just starting out I don’t recommend using the older version unless you have reason to learn/use it. See @jenrodrigues’s link above for info on this version of the framework.

  2. Angular - 8.2.14 is latest as of this writing, which is the current/new/better version of the framework that is a ground up re-write of the framework. This version builds upon the previous to scale better, and fixed a number of issues fund with the first one. See @astv99’s link above for more info for this version of the framework. I recommend using this version.

PS. Version 9 should be arriving within a few weeks of this post, as its currently available as a release candidate, which means its very close to being officially released. This version should bring in a newer render that will provide performance improvements and a better api for making the framework better in the future.

2 Likes

Now I got it right. Thanks @bradtaniguchi .

1 Like

thanks for the info. However I have an issue with the npm. Please see below

npm WARN deprecated core-js@2.6.10: core-js@<3.0 is no longer maintained and not recommended for usage due to the number of issues. Please, upgrade your dependencies to the actual version of core-js@3.
npm WARN deprecated fsevents@1.2.9: One of your dependencies needs to upgrade to fsevents v2: 1) Proper nodejs v10+ support 2) No more fetching binaries from AWS, smaller package size
[ …] / extract:fsevents: sill extract fsevents@^1.2.7 extracted to C:\Users\hisham99[ …] \ extract:fsevents: sill extract fsevents@^1.2.7 extracted to C:\Users\hisham99\tic-tac\node_modules.[ …] \ extract:fsevents: sill extract fsevents@^1.2.7 extracted[ …] \ extract:fsevents: sill extract fsevents@^1.2.7 extracted to C:\Users\hisham99\tic-tac\node_modules.staging\fsevents-ef807[ …] \ extract:fsevents: sill extract fsevents@^1.2.7 extracted to C:\Users\hisham99\tic-tac\node_modules.staging\fsevents-1c2ca557 (180604ms)

npm WARN deprecated core-js@2.6.10: core-js@<3.0 is no longer maintained and not recommended for usage due to the number of issues. Please, upgrade your dependencies to the actual version of core-js@3.

npm WARN deprecated fsevents@1.2.9: One of your dependencies needs to upgrade to fsevents v2: 1) Proper nodejs v10+ support 2) No more fetching binaries from AWS, smaller package size
[ …] / extract:fsevents: sill extract fsevents@^1.2.7 extracted to C:\Users\hisham99[ …] \ extract:fsevents: sill extract fsevents@^1.2.7 extracted to C:\Users\hisham99\tic-tac\node_modules.[ …] \ extract:fsevents: sill extract fsevents@^1.2.7 extracted[ …] \ extract:fsevents: sill extract fsevents@^1.2.7 extracted to C:\Users\hisham99\tic-tac\node_modules.staging\fsevents-ef807

core-js@2.6.10 postinstall C:\Users\hisham99\tic-tac\node_modules\babel-runtime\node_modules\core-js
node postinstall || echo “ignore”

core-js@3.2.1 postinstall C:\Users\hisham99\tic-tac\node_modules\core-js
node scripts/postinstall || echo “ignore”

core-js@2.6.10 postinstall C:\Users\hisham99\tic-tac\node_modules\karma\node_modules\core-js
node postinstall || echo “ignore”

@angular/cli@8.3.19 postinstall C:\Users\hisham99\tic-tac\node_modules@angular\cli
node ./bin/postinstall/script.js

npm WARN rollback Rolling back readable-stream@2.3.6 failed (this is probably harmless): EPERM: operation not permitted, lstat ‘C:\Users\hisham99\tic-tac\node_modules\karma\node_modules\fsevents\node_modules’
npm WARN rollback Rolling back node-pre-gyp@0.12.0 failed (this is probably harmless): EPERM: operation not permitted, lstat ‘C:\Users\hisham99\tic-tac\node_modules\karma\node_modules\fsevents\node_modules’
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.9 (node_modules\webpack-dev-server\node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.9: wanted {“os”:“darwin”,“arch”:“any”} (current: {“os”:“win32”,“arch”:“x64”})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.9 (node_modules\watchpack\node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.9: wanted {“os”:“darwin”,“arch”:“any”} (current: {“os”:“win32”,“arch”:“x64”})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.9 (node_modules\karma\node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.9: wanted {“os”:“darwin”,“arch”:“any”} (current: {“os”:“win32”,“arch”:“x64”})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.9 (node_modules@angular\compiler-cli\node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.9: wanted {“os”:“darwin”,“arch”:“any”} (current: {“os”:“win32”,“arch”:“x64”})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@2.1.2 (node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.1.2: wanted {“os”:“darwin”,“arch”:“any”} (current: {“os”:“win32”,“arch”:“x64”})

added 1191 packages from 1051 contributors and audited 18872 packages in 593.166s

6 packages are looking for funding
run npm fund for details

found 0 vulnerabilities

‘git’ is not recognized as an internal or external command,
operable program or batch file.

I’ve managed to create the file on visual studio. Should I ignore the previous warning messages?

Thanks

These are warning messages that can be ignored. Your welcome to look into each one individually to see if it pertains to what your doing, but generally you can ignore them.

any ideas to fix this. My local host 4200 was not working.