"dependencies": {
"@meanie/angular-analytics": "^2.0.0",
"@meanie/angular-api": "^3.0.1",
"@meanie/angular-convert": "^2.0.1",
"@meanie/angular-duplicate-requests-filter": "^2.0.0",
"@meanie/angular-focus": "^2.0.0",
"@meanie/angular-key-codes": "^2.0.0",
"@meanie/angular-log": "^2.0.0",
"@meanie/angular-modal": "^3.0.0",
"@meanie/angular-storage": "^2.0.1",
"@meanie/angular-store": "^2.0.1",
"@meanie/angular-url": "^2.0.1",
"angular": "1.6.8",
"angular-animate": "1.6.8",
"angular-cookies": "1.6.8",
"angular-messages": "1.6.8",
"angular-sanitize": "1.6.8",
"angular-touch": "1.6.8",
"angular-ui-router": "^0.4.2",
"fastclick": "^1.0.6",
"marked": "^0.3.9",
"meanie-angular-form-controls": "^1.4.5",
"moment": "^2.20.1",
"ng-infinite-scroll": "^1.3.0",
"raven-js": "^3.21.0"
},
"devDependencies": {
"babel-polyfill": "^6.23.0",
"babel-preset-es2015": "^6.24.0",
"browser-sync": "^2.18.6",
"chalk": "^1.1.3",
"del": "^2.2.2",
"git-rev-sync": "^1.8.0",
"gulp": "git+https://github.com/gulpjs/gulp#4.0",
"gulp-angular-templatecache": "^2.0.0",
"gulp-autoprefixer": "^3.1.1",
"gulp-babel": "^6.1.2",
"gulp-concat": "^2.6.1",
"gulp-csso": "^3.0.0",
"gulp-file": "^0.4.0",
"gulp-htmlclean": "^2.7.16",
"gulp-inject": "^4.3.0",
"gulp-ng-annotate": "^2.1.0",
"gulp-ng-constant": "^1.1.0",
"gulp-plumber": "^1.1.0",
"gulp-preprocess": "^2.0.0",
"gulp-remove-empty-lines": "^0.0.8",
"gulp-remove-html-comments": "^1.0.1",
"gulp-rename": "^1.2.2",
"gulp-sass": "^3.1.0",
"gulp-sourcemaps": "^2.4.1",
"gulp-uglify": "^2.1.2",
"gulp-wrapper": "^1.0.0",
"http-proxy-middleware": "^0.17.4",
"merge-stream": "^1.0.1",
"npm-run-all": "^4.0.2",
"mime": "^1.3.4",
"netlify-cli": "^1.2.2",
"replace-in-file": "^2.5.0",
"rimraf": "^2.6.1",
"s3-cli": "^0.13.0",
"serve-static": "^1.12.1",
"yargs": "^10.0.3"
}
Do you want to request a feature or report a bug?
Bug
What is the current behavior?
Installation of packages fails when installing in production, Yarn 1.3.2 errors with:
Error: Cannot find module 'are-we-there-yet'This does not happen with Yarn 0.18.1, where the installs complete successfully.
If the current behavior is a bug, please provide the steps to reproduce.
These are the relevant dependencies for a particular package that fails:
What is the expected behavior?
For the Yarn install to work.
Please mention your node.js, yarn and operating system version.
Node.JS 8.9.3, Yarn 1.3.2, the build was failing on Netlify VM's.
Ref #761