Using npm and n

I like to have the same results over different environments that is why I highly recommend using versioning tools and not only git but also stuff to install dependencies like npm and the hability to handle different target versions like n. I might be wrong but this ends up being very similar like using bundler,gemfile and rvm to handle ruby versions (more on that in another post). Anyways back to the journey:

Things that were required

In the previous example, #simple is just an easy way to verify some logic without getting packages installed. I think as a good practice it is very important to understand how testing the same stuff, in the same environment (possibly very close) and many other factors deeply affects the long term success of a testing effort or project and how easy it will be to maintained in the future. That is why my first package will be n so I will allow to test the same stuff over different NodeJS versions and hopefully get the same or very similar results.

As you can see in the above image I'm able to use the latest version of NodeJS and also the LTS version of it which also differs from the version I currently have install in the system with the OS package manager.

In case you miss the first post of this series:

Journal of posts and articles

• The journey of the coder
• The journey of the coder (2)

@raserrano - Developer

	@kedjom-keku	Conservation Association
	@treeplanter	Fund-raising upvoting bot
	@forestfriendly	Water Saving bees