scribr v1.0.0

• Scribr

• [https://gitlab.com/reedrichards-javascript/gatsby/grimoire]

• Development

• Node Version: 12.16.1 LTS

** Install Node

*** using nvm

**** [https://github.com/nvm-sh/nvm#installing-and-updating] #+BEGIN_SRC bash :results output curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.35.3/install.sh | bash

 #+END_SRC

 #+RESULTS:
 #+begin_example
 => nvm is already installed in /home/rob/.nvm, trying to update using git
 

=> => Compressing and cleaning up git repository

 => nvm source string already in /home/rob/.bashrc
 => bash_completion source string already in /home/rob/.bashrc
 => You currently have modules installed globally with `npm`. These will no
 => longer be linked to the active version of Node when you install a new node
 => with `nvm`; and they may (depending on how you construct your `$PATH`)
 => override the binaries of modules installed with `nvm`:

 /usr/local/lib
 ├── gatsby@2.19.3
 ├── UNMET PEER DEPENDENCY react@^16.4.2
 ├── UNMET PEER DEPENDENCY react-dom@^16.4.2
 ├── tldr@3.3.2
 ├── typescript@3.8.3
 ├── typescript-language-server@0.4.0
 └── yarn@1.21.1
 => If you wish to uninstall them at a later point (or re-install them under your
 => `nvm` Nodes), you can remove them from the system Node as follows:

  $ nvm use system
  $ npm uninstall -g a_module

 => Close and reopen your terminal to start using nvm or run the following to use it now:

 export NVM_DIR="$HOME/.nvm"
 [ -s "$NVM_DIR/nvm.sh" ] && \. "$NVM_DIR/nvm.sh"  # This loads nvm
 [ -s "$NVM_DIR/bash_completion" ] && \. "$NVM_DIR/bash_completion"  # This loads nvm bash_completion
 #+end_example

**** [https://github.com/nvm-sh/nvm#verify-installation] #+BEGIN_SRC bash command -v nvm

 #+END_SRC

**** install node 12.16.1 #+BEGIN_SRC bash nvm install 12.16.1

 #+END_SRC