Fix yarn.lock for next#7341
Merged
thorn0 merged 1 commit intoprettier:nextfrom Jan 15, 2020
Merged
Conversation
alexander-akait
approved these changes
Jan 15, 2020
Member
|
@fisker WDYT of integrating the repo with {
"scripts": {
"fix": "yarn fix:eslint && yarn fix:prettier && fix:yarn-deduplicate",
"fix:eslint": "eslint \"**/*.*\" --fix",
"fix:prettier": "prettier --write \"**/*.*\"",
"fix:yarn-deduplicate": "yarn-deduplicate --strategy=fewer",
"lint": "yarn lint:eslint && yarn lint:prettier && yarn lint:tsc && yarn lint:yarn-deduplicate",
"lint:eslint": "eslint --report-unused-disable-directives \"**/*.*\"",
"lint:prettier": "prettier --check \"**/*.*\"",
"lint:tsc": "tsc -p .",
"lint:yarn-deduplicate": "yarn-deduplicate --list --fail --strategy=fewer",
},
"devDependencies": {
"...": "...",
"yarn-deduplicate": "^1.1.1"
},
"...": "..."
}This helps continuously maintain a clean |
Member
|
This lock file is still unstable. The issue is caused by yarnpkg/yarn#7770 and |
Member
thorn@THORN-LNV:/mnt/d/dev/prettier-fisker$ rm -rf node_modules/ yarn.lock && yarn cache clean && yarn
yarn cache v1.21.1
success Cleared cache.
Done in 10.75s.
yarn install v1.21.1
info No lockfile found.
[1/5] Validating package.json...
[2/5] Resolving packages...
warning cspell > comment-json > [email protected]: `json-parser` is deprecated. Please use `comment-json` instead
warning jest > jest-cli > jest-config > jest-environment-jsdom > jsdom > [email protected]: use String.prototype.padStart()
warning [email protected]: This package has been deprecated and is no longer maintained. Please use @rollup/plugin-node-resolve.
[3/5] Fetching packages...
warning [email protected]: Invalid bin entry for "sha.js" (in "sha.js").
info [email protected]: The platform "linux" is incompatible with this module.
info "[email protected]" is an optional dependency and failed compatibility check. Excluding it from installation.
[4/5] Linking dependencies...
warning " > [email protected]" has incorrect peer dependency "@angular/compiler@^6.0.0 || ^7.0.0".
[5/5] Building fresh packages...
success Saved lockfile.
Done in 61.25s.
thorn@THORN-LNV:/mnt/d/dev/prettier-fisker$ git status
On branch next-lock
Your branch is up to date with 'origin/next-lock'.
Changes not staged for commit:
(use "git add <file>..." to update what will be committed)
(use "git checkout -- <file>..." to discard changes in working directory)
modified: yarn.lock
no changes added to commit (use "git add" and/or "git commit -a")
|
Member
Author
|
I don't mean to regenerate new lock, old one changes when run |
lock
Bot
added
the
locked-due-to-inactivity
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Lock file in
nextseems not right.docs/directory)changelog_unreleased/*/pr-XXXX.mdfile followingchangelog_unreleased/TEMPLATE.md.✨Try the playground for this PR✨