Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

yarn.lock not saved #3981

Closed
rarkins opened this issue Jul 21, 2017 · 1 comment
Closed

yarn.lock not saved #3981

rarkins opened this issue Jul 21, 2017 · 1 comment

Comments

@rarkins
Copy link
Contributor

rarkins commented Jul 21, 2017

Do you want to request a feature or report a bug?

bug

What is the current behavior?

yarn install completes successfully but no yarn.lock is written and no "Saved lockfile" message is displayed.

If the current behavior is a bug, please provide the steps to reproduce.

Here is an example package.json:

```json { "name": "react-element-to-jsx-string", "version": "11.0.0", "description": "Turn a ReactElement into the corresponding JSX string.", "main": "dist/index.js", "scripts": { "build": "babel ./src/ --ignore=*.spec.js --source-maps --out-dir ./dist/", "lint": "node_modules/.bin/eslint .", "lint:fix": "npm run lint -- --fix", "flow": "flow", "precommit": "lint-staged", "prepublish": "npm run build", "prebuild": "mkdir -p dist && rm -rf ./dist/*", "prettier:fix": "prettier --write --single-quote --trailing-comma es5 \"{src/**/*.js,package.json}\"", "test": "jest && npm run lint", "test:watch": "jest --watch", "release": "./release.sh" }, "lint-staged": { "*.js": [ "prettier --write --single-quote --trailing-comma es5", "git add" ] }, "author": { "name": "Algolia, Inc.", "url": "https://github.com/algolia" }, "license": "MIT", "repository": "algolia/react-element-to-jsx-string", "devDependencies": { "babel-cli": "6.24.1", "babel-eslint": "7.2.3", "babel-jest": "20.0.3", "babel-plugin-lodash": "3.2.11", "babel-preset-es2015": "6.24.1", "babel-preset-flow": "6.23.0", "babel-preset-react": "6.24.1", "babel-preset-stage-2": "6.24.1", "babel-register": "6.24.1", "conventional-changelog-cli": "1.3.2", "doctoc": "1.3.0", "eslint": "4.2.0", "eslint-config-algolia": "12.0.0", "eslint-config-prettier": "2.3.0", "eslint-plugin-import": "2.7.0", "eslint-plugin-jest": "20.0.3", "eslint-plugin-prettier": "2.1.2", "eslint-plugin-react": "7.1.0", "expect": "1.20.2", "flow-bin": "0.50.0", "husky": "0.14.3", "jest": "20.0.4", "json": "9.0.6", "lint-staged": "4.0.2", "mversion": "1.10.1", "prettier": "1.5.3", "react": "15.6.1", "react-dom": "15.6.1", "react-test-renderer": "15.6.1" }, "peerDependencies": { "react": "^0.14.8 || ^15.0.1" }, "dependencies": { "collapse-white-space": "^1.0.3", "is-plain-object": "^2.0.4", "lodash": "^4.17.4", "sortobject": "^1.0.0", "stringify-object": "^3.2.0" } } ```

Then run yarn install --ignore-scripts. This fails to generate a yarn.lock for me on both Ubuntu 16.04 and OSX.

What is the expected behavior?

yarn.lock should be written

Please mention your node.js, yarn and operating system version.

yarn v0.27.5. Tried on both Ubuntu 16.04 and OSX. Also tried on both node 8.x and 6.x. Most recently trying on v6.11.1.

@rarkins
Copy link
Contributor Author

rarkins commented Jul 21, 2017

Sorry for false alarm, I have found a --install.pure-lockfile true .yarnrc :(

@rarkins rarkins closed this as completed Jul 21, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant