Here is my feedback setting up the Poudre Basin Information development workspace using InfoMapper. This involves installing node.js (and npm) software from scratch. However, I am updating existing InfoMapper files that were copied from my previous machine. I am following the "Getting Started" documentation.
The link to node.js does not actually go to the download page. Need to fix.
Indicate that the Windows PATH is automatically updated by the installer but a new window must be opened to recognize.
Josh seemed to be confused by the installation into global, but I'm sure I followed these instructions the previous time I set up. Review and update the documentation related to global, versions, etc.
Explain that the local version of Angular will be used based on the InfoMapper package.json.
Provide clear instructions about providing npm credentials. Show an example with OpenWaterFoundation filled in so it can be copied and pasted. This needs to be clear on the dev library documentation and for InfoMapper (and probably InfoMapper Builder). You can add a somewhat verbose section in the dev library README and link to that, or something else. This is REALLY EASY to forget and get lost in the web pages.
Explain using npm --force.
Maybe add specific troubleshooting Q&A such as using npm ls. Perhaps have a troubleshooting item for installing the library the first time?
Here is my feedback setting up the Poudre Basin Information development workspace using InfoMapper. This involves installing
node.js(andnpm) software from scratch. However, I am updating existing InfoMapper files that were copied from my previous machine. I am following the "Getting Started" documentation.node.jsdoes not actually go to the download page. Need to fix.PATHis automatically updated by the installer but a new window must be opened to recognize.package.json.npmcredentials. Show an example withOpenWaterFoundationfilled in so it can be copied and pasted. This needs to be clear on the dev library documentation and for InfoMapper (and probably InfoMapper Builder). You can add a somewhat verbose section in the dev library README and link to that, or something else. This is REALLY EASY to forget and get lost in the web pages.npm --force.npm ls. Perhaps have a troubleshooting item for installing the library the first time?