You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* feat: support yarn v2
Since Yarn Berry uses NPM for audits, the Yarn auditer is not supported.
Yarn Classic uses a JSON-lines format for audit results.
Yarn Berry audit cmd: `yarn npm audit --all --recursive --json`
The following work is still required:
- Make Yarn Berry audits use npm-auditer.js logic for runProgram
- Have the Yarn Berry tests detect that Yarn Berry should be used
(unknown reason why it thinks it's Yarn Classic)
* docs: Add support for Yarn Berry in README
* fix: pass cwd to yarn version check
* fix: skip yarn berry tests on incompatible node versions
Co-authored-by: Quinn Turner <[email protected]>
When creating Yarn Berry tests, there are several files and folders that may generate that are not necessary for auditing using `yarn npm audit --all --recursive --json`.
4
+
5
+
- .pnp.js
6
+
7
+
- .yarn/cache
8
+
9
+
Consider manually deleting them before committing.
10
+
11
+
Also, the `.yarn/releases/yarn-berry.cjs` file in each project re-exports the `yarn-berry.cjs` file at the root of tests.
12
+
Re-exporting the file reduces duplication and version mismatching for tests.
13
+
Currently, this project is set up to use the latest version v2.4.0 (at the time of writing this, Dec 6th, 2020).
0 commit comments