The other day we were discussing the "non-trivial" process of getting the development environment set up.
After a lot of trial and error, I got it working on a recently re-installed Linux Mint system.
Perhaps rather than (or alongside) the "follow the link above and install it [node.js] on your system" instruction on the pattern design tutorial, we could have something like the following:
Developers are likely to have some or all of these software packages installed already.
On Linux systems that use APT (Debian, Ubuntu, Linux Mint etc.), install the software using the terminal commands:
sudo apt-get install npm
sudo apt-get install nodejs
sudo apt-get install git
Configure "git" to access the software repositories:
git config --global user.email "firstname.lastname@example.org"
git config --global user.name "your-user-name"
Before setting up the development environment, you will need to create and set permissions for a library directory that the setup script needs to write to:
sudo mkdir /usr/local/lib/node_modules
sudo chmod 777 /usr/local/lib/node_modules/
(apologies for not formatting that in any way - I don't know gitter)
Perhaps @docspencer77 could write something similar to help with the Windows installation process based on her recent experience getting started?
@tdmpaton and @IAmTheBlurr I took the time yesterday to read documentation/support stuff, uninstall, reinstall (x3), change versions, etc., etc. I'm glad to document my discoveries and try to help the folks wielding Windows get past some obstacles. From my perspective, the biggest issues are that the "how to" instructions are not in one place, and there are several choices with several pieces of the process that you don't know you've made till after it doesn't work (or blows up).
I haven't walked through the MS guide on the process
but will do that. It's Visual Studio-centric, and I've been using VS Code for the Node.JS stuff, but in general I've used Visual Studio lots more that VS Code.
@joostdecock Should we put together a "How to" and link it from the "Setting up your Development Environment"? And maybe we want to take this conversation over to discord?
@DocSpencer77 I have my own node/express app project which I deploy both to a production linux server and run locally for testing on a Windows 10 machine. The instructions on microsofts website can be simplified, the requirement for using VS Code, Visual Studio, or any IDE (I use WebStorm and all other JetBrains IDEs personally) can be subtracted from a well written tutorial.
I spend a hell of a lot of time writting documentation for various purposes, and I find it a joyful activity personally, so I should be able to be useful where needed.
@joostdecock Agreed, test first write documentation after.
Btw, I don't know if I mentioned this when we spoke before but my day job is as a test automation architect. I write frameworks, infrustructure, and interfaces to test systems (in the Quality Assurance sense).
When you're ready to start thinking about serious QA efforts, let me know. I've been doing QA professionally in one capacity or another for 21 years.
I spend a hell of a lot of my time working with automating the testing of web UI systems currently (at my day job).