It would be good if the docs and --help output could mention that nvm install installs and uses the given Node version. I've probably wasted hours typing nvm install __ && nvm use __, - just discovered the second part has been unnecessary since this was fixed in 2014 :)

Steps to reproduce

Run asdf. In help output a line is printed for the asdf env command:

asdf env <command> [executable]      Prints or runs an executable under a command environment

I would assume <command> is an arbitrary command. But from what I can tell needs to be a plugin name or a shim name? I'm also not sure how this differs from executing the shim directly.

FY

Is your feature request related to a problem? Please describe.

more documentation and tutorial about how can be used
Describe the solution you'd like

video tutorials
**Describe alternatives you've consider

• Add labels appropriate to the issue
  bug

• Describe the expected behaviour and the actual behaviour
  .....
  ervice/rabbitmq created
  deployment.extensions/session-db created
  service/session-db created
  deployment.extensions/shipping created
  service/shipping created
  deployment.extensions/user-db created
  service/user-db created
  deployment.extensions/user created
  service/user created
  Er

When i Installing Document Server for Linux on CentOS7.5.
Reference:https://helpcenter.onlyoffice.com/server/linux/document/linux-installation-centos.aspx
In the end,the document server is ok，
but When I test editing files，
ws://XXXX/5.5.1-76/doc/b81fdff747a247929253f4701a92bc521588227954180/c/208/zp1umjpc/websocket
This link has been pending.
Centos7.5：port all open，firewall is closed.
Wha

As #103 showed, we should have clear instructions as to how to add a frontend application inside our NoDock environment.

We should try to make sure users are not installing ioBroker with an unsupported node version.
In detail we support:

• node 8.12+
• node 10.9+
• no node 9, no node 11

The installer should stop installation if this is not met, BUT (especially for dev environments) we should allow an optional parameter like "-ignore-node-version-restrictions" or such to bypass the check. This is then logged i

Hi, I'm wanting to use Koop for integrating with the Waze live feed. After reading through the readme, I was totally lost about how to even start using Koop.

I'd really like to see more detailed documentation or a getting started guide. Additionally I'd be interested in helping to get a dedicated Waze repository up running.

In the Quick usage guide Option 2, speak to use this command:

curl -L https://github.com/ambientum/cli/releases/download/v0.1.1/amb-`uname -s` -o /usr/local/bin/amb

but is the v before the release number gives an invalid url, the correct url is:

curl -L https://github.com/ambientum/cli/releases/download/0.1.1/amb-`uname -s` -o /usr/local/bin/amb

We don't watch them much, but if the dailies are unstable, the instability will be seen in PR builds.

@AshCripps was reviewing them for a while, and with some fixes and flaky test marking, I thought they started to go green, but I might misremember.

job: https://ci.nodejs.org/job/node-daily-master/

This needs a bit of watching, and it doesn't take build-wg permissions, so if anyone is loo

When fixing a bug I added a reproducer project and discovered that if the description is empty in the package.json file like so {"description": ""} node-deb crashes. Not super-critial, and people should really have a description. The error message was pretty good also so it was easy to just add a description. 👍 for good error messages.

Survey showed people don't know how to report issues:

Some ideas

1. add link on Node.js org website
2. add info in benchmarking repo
3. add email address
4. Communication/publication