This uses a candidate model for determining an suitable cache directory. This is different from the current approach with eagerly chooses a cache directory. If that directory isn't accessible for some reason (i.e. permissions) we have to bail out. With this approach we can try a prioritised list of candidate directories. Additionally this address the case where npm cache config is blank. Fixes #1781
| Name |
Last commit
|
Last update |
|---|---|---|
| bin | Loading commit data... | |
| lib | Loading commit data... | |
| media | Loading commit data... | |
| scripts | Loading commit data... | |
| src | Loading commit data... | |
| test | Loading commit data... | |
| .editorconfig | Loading commit data... | |
| .eslintrc.json | Loading commit data... | |
| .gitattributes | Loading commit data... | |
| .gitignore | Loading commit data... | |
| .gitmodules | Loading commit data... | |
| .travis.yml | Loading commit data... | |
| CHANGELOG.md | Loading commit data... | |
| CONTRIBUTING.md | Loading commit data... | |
| ISSUE_TEMPLATE.md | Loading commit data... | |
| LICENSE | Loading commit data... | |
| README.md | Loading commit data... | |
| TROUBLESHOOTING.md | Loading commit data... | |
| appveyor.yml | Loading commit data... | |
| binding.gyp | Loading commit data... | |
| package.json | Loading commit data... |