It can happen that npm install -g <package-name> reports an EPERM error. This means that npm isn't allowed to write to the directory without administrator rights. To fix this npm needs to be configured so that it uses a different folder.
npm config set prefix "%AppData%/npm"
| # Strengths | |
| - No leftover files | |
| - Solved by passing temporary directories between plugins (i.e. tasks) | |
| # Weaknesses | |
| - No parallel plugin execution | |
| - No parallel tasks: Independent tasks could execute in parallel | |
| - No parallel builds: Can't decouple independent parts, e.g. unit tests from rest | |
| - Code base issues |
If a request fails the server SHOULD answer with an error which is stored in the "error" property. The simplest form ist just a string with the type of the error:
{
"error": "csrfTokenInvalid"
}Error types SHOULD be in camelCase starting with a lowercase letter and SHOULD NOT end with "Error".
The more elaborate form is providing an error object. Error objects MUST hold a "type" property with the type of the error:
Popular node packages that use dasherized names in the file system.
(Click to see a sample dasherized file from that project)