![]() By using these stepping-stone JavaScript 1.6-1.9 releases as a way to test out bug fixes and functionality both users, and browser vendors, can get a better picture of the changes that will be occurring in the language. However, that hasn’t stopped browsers from implementing JavaScript features (such as getters and setters in Opera and Safari).Ī big goal of Mozilla is to try implementing difficult ECMAScript features, helping to lead other browsers by example. Of course no other browser will support another JavaScript 1.6-1.9, since they aren’t obligated to support JavaScript. JavaScript 1.6-1.9 are just code names for the interim versions of ECMAScript (JavaScript on Gecko) that are leading up to JavaScript 2.0 (ECMAScript 4). However, all modern browsers support a version of ECMAScript – at least version 3. It should be noted that the only browser that supports ‘JavaScript’ are Mozilla-based ones. Safari supports a language that is equivalent to ECMAScript 3 + Getters and Setters + misc.Opera supports a language that is equivalent to ECMAScript 3 + Getters and Setters + misc.The next version of Firefox will support JavaScript 1.9 (1.8 + To be determined).Firefox 3.0 supports JavaScript 1.8 (1.7 + Generator Expressions + Expression Closures + misc.).Firefox 2.0 supports JavaScript 1.7 (1.6 + Generator + Iterators + let + misc.).Firefox 1.5 supports JavaScript 1.6 (1.5 + Array Extras + E4X + misc.).Firefox 1.0 supports JavaScript 1.5 (ECMAScript 3 equivalent).IE 8 supports JScript 6 (which is equivalent to ECMAScript 3, JavaScript 1.5 – more bug fixes over JScript 5).IE 6-7 support JScript 5 (which is equivalent to ECMAScript 3, JavaScript 1.5).Node can either be or not be natively installed in the machine, it does not make a difference for this use case.With the recent talk of JavaScript 1.9 there’s been some confusion as to what exactly that version means – especially in relation to other browsers. nvm exec is equivalent to Ī normal nvm usage workflow (and the one we are going to use to manage different projects' Node versions) would be to install each project's Node version and then execute it in an independent project dedicated shell.If you are not familiar with nvm commands, keep in mind that: It allows the user to install multiple Node versions on its machine and then use different versions in separate shells simultaneously. Nvm is a Node version manager command line tool. I found two concepts that seemed promising to be used together: It was in that moment that I started to search for a possible solution to manage different Node and Angular versions for different projects. Besides, it's good practice to maintain versions during development, unless explicitly wanting to change them. ![]() When downgrading/upgrading Angular CLI, you also need to make sure the Node version being used is compatible. An Angular project's CLI version is in the package.json file, but what about the Node version? That is a piece of information that must be documented, and as we all know well, documentation is almost always left behind.Įach Angular version is compatible with a range of Node versions. Not only is this a time-wasting process, it is susceptible to errors from missing information. I must admit that the first time this switch was needed, I naively downgraded both Node and Angular CLI… Only to then upgrade them again when I went back to working on my current project. ![]() So I eventually came to a point where I needed to actively work on my current project but be able to quickly switch back to any of the other projects. Not only that, but all of these projects had at least one Node based component and a big part of them also used Angular as their Frontend framework. In my line of work as a Web Engineer, I have leaped through a decent amount of projects in a not so big amount of time. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |