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. Not only that, but all of t...
For further actions, you may consider blocking this person and/or reporting abuse
There's also nsv which I found to work better in Windows, especially for upgrading npm.
I have heard of it, but I have never used it, I'll be sure to take a look at it someday.
What's the difference between them for that specific case of upgrading npm?
With
nvmI had to usenpm-windows-upgradepackage, while with nvs you can simply donpm i -g npm. I also had trouble with the antivirus (McAfee) which had to be turned off while installing another version of node with nvm.Interesting to know... I've just used
nvmon a Linux environment, never got to trynvm-windows, but now I'll keep that in mind.Thanks for the heads up!
Instead of creating scripts in every project of yours to run the local version of the angular cli, you can use the npx package! You can install it globally and then whenever you are inside a project with node modules you can run "npx the-tool-name" and it will run the tool local to the project. (In this instance if "the-tool-name" was ng, it would run the local version of the angular cli without the need to add ng as a script in the package.json)
npxis really an useful tool, thanks for the tip!Hey Patricia, just came across this article now and know the pain of operating across multiple angular version and node projects so this is very handy.
I set it up on my linux for my own personal projects and it seems after different node versions via nvm are installed and I run the "nvm run npm" start in the angular project directory I got a Cannot find module npm issue. I raised a ticket on the nvm github and yesterday I was told that after running "nvm use node version" its not necessary to run "nvm run npm start" due to the prior "nvm use" command being used.
Not sure if things have changed since you first uploaded this or not but wanted to pass that onto folks :>
If you are interested in the details of it the ticket can be found on: github.com/nvm-sh/nvm/issues/2284
Thanks now
Hi. Yes, you're right, after
nvm useyou can execute onlynpm startand it will use the Node version you selected.But actually the correct command to run npm as you were trying would be
nvm exec npm start(notnvm run), maybe that's why you were getting an error? I see I have that command wrong in one of the sections of the post, I have anvm runwhere anvm execshould be (I'm going to edit that). Running the commands like this is only usefull if you have a.nvmrcfile to avoid having to executenvm useevery time. But like you said, if you runnvm use, then you can actually just use the normalnodeandnpmcommands!I just use docker. Define an image version as a variable, and you can easily manage all your infrastructure as code.
Hi Patryk! Yeah, that was also my original approach (and the one I actually keep using the most). Do you use mounted volumes in your containers? I do, and sometimes the file system access to the host makes read/write operations slow, and that was what made me look for a different approach.
I use both bind mounts for development (in my Python and node containers), and named volumes in dev and production, e.g. for my databases.
I use Linux for development and production, and I've never noticed any performance issues.
Same here, regarding the volumes. But when in Windows with a bind mount for development, a simple
npm installwould take a lot longer than when run in the host. Probably Windows related...Why use nvm execute when you could just use npm? Considering you've switched the node versions already.
By "switched the node versions already" do you mean executed
nvm use [version]? Because if so, then when you open a new terminal, the version nvm will be using will no longer be the one you just defined. It will be the one to which the nvmdefaultalias is pointing to.The combination
.nvmrcfile +nvm exec/nvm runavoids having to runnvm useevery time.Got you, yeah meant after nvm use. For what it's worth though there's a tool to automatically switch versions when you have a .npmrc file
github.com/wbyoung/avn, you could have a script to do that as well.
a bit offtopic but since this is about Angular versions, is there a way to know which versions of TypeScript are supported in the current Angular version?
You can check the supported TypeScript versions for an Angular version in the
@angular/compiler-cli/package.json:There seems to be a way to disable this version checking in case you want to install a version outside of that range. But I guess you should do that at your own risk.
oh that's helpful. Thanks @patricepeartree
How does nvm will affect the internal operations of Visual Code to create components, services etc. ?
what about when you want to create new angular project using
"ng new my_new_project"
what you gonna do when you still don't have local directory?
Well, I guess you can have some workarounds for that. You can
npm inita directory just to be able to install locally the Angular version you want, and then use that one tong newyour new project. Or you can leverage Docker with mounted volumes and create a project from within a container with your desired Angular version.