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

Release/v7.6.1 #2825

Merged
merged 15 commits into from
Mar 4, 2021
Merged

Release/v7.6.1 #2825

merged 15 commits into from
Mar 4, 2021

Conversation

ruyadorno
Copy link
Contributor

v7.6.1 (2021-03-04)

BUG FIXES

DOCUMENTATION

DEPENDENCIES

wraithgar and others added 14 commits March 4, 2021 15:54
The lifecycle events section was very out of date, and lots
of other cleanup needed to happen too

PR-URL: #2690
Credit: @wraithgar
Close: #2690
Reviewed-by: @ruyadorno
I checked cli's code with Typescript using the tsconfig below. The
compiler found a few arguments that are not used, so I removed them. In
the case of `npm whoami`, it is clearer that it ignores its `args`
and instead relies on `npm.flatOptions`.

```json
{
    "compilerOptions": {
        "moduleResolution": "node",
        "module": "commonjs",
        "resolveJsonModule": true,
        "target": "es2019",
        "noImplicitAny": false,
        "noImplicitThis": true,
        "strict": true,
        "maxNodeModuleJsDepth": 0,
        "noEmit": true,
        "allowJs": true,
        "checkJs": true,
        "types": ["node"],
        "lib": ["esnext"]
    },
    "include": ["lib"]
}
```

PR-URL: #2766
Credit: @sandersn
Close: #2766
Reviewed-by: @nlf, @ruyadorno, @Matausi29
Instead of files randomly requiring the npm singleton,
we pass it where it needs to go so that tests don't need
to do so much require mocking everywhere

PR-URL: #2772
Credit: @wraithgar
Close: #2772
Reviewed-by: @ruyadorno
1. Set the shebang to /usr/bin/env bash instead of /bin/sh (which might
   be dash or some other shell)
2. Use Unix-style line endings, not Windows-style (Cygwin accepts
   either, but mingw bash sometimes objects, and WSL bash always does)
3. Test against paths using wslpath if available, but still pass win32
   paths to node.exe, since it is a Windows binary that only knows how
   to handle Windows paths.

This makes npm as installed by the Node.js Windows MSI installer behave
properly under WSL, Cygwin, MINGW Git Bash, and the internal MINGW Git
Bash when posix CLI utilities are exposed to the cmd.exe shell.

The test is not quite as comprehensive as I'd like.  It runs on the
various Windows bash implementations if they are found in their expected
locations, skipping any that are not installed.  Short of shipping
mingw, cygwin, and wsl as test fixtures, I'm not sure how we could do
much better, however.  At least, we can use this test to assist debug
and catch issues on Windows machines (ours or users who report
problems).

PR-URL: #2789
Credit: @isaacs
Close: #2789
Reviewed-by: @nlf
The searchopts get parsed and added to the query elsewhere, they're not
part of the `include` array they are an extra querystring that is added
to the search request.

PR-URL: #2803
Credit: @wraithgar
Close: #2803
Reviewed-by: @ruyadorno
pacote expects a **where** option that sets the cwd for all its
operations, ref: https://github.com/npm/pacote#options

This change properly sets that option in libnpmdiff options that will
then properly forward it to pacote, this is specially important for when
reading local file system specs.

PR-URL: #2822
Credit: @ruyadorno
Close: #2822
Reviewed-by: @wraithgar
This causes a `cb() not called` error as the promisified
function explodes silently.

PR-URL: #2824
Credit: @wraithgar
Close: #2824
Reviewed-by: @ruyadorno
@ruyadorno ruyadorno requested a review from a team as a code owner March 4, 2021 21:55
@ljharb
Copy link
Contributor

ljharb commented Mar 4, 2021

Shouldn't 3c9a589 be semver-minor?

@ruyadorno
Copy link
Contributor Author

Shouldn't 3c9a589 be semver-minor?

Wasn't so sure about it so I decided to go with a semver-patch under the light that npm explain should have been explaining this since its inception 😅 but I def see the case for it to also be considered a new feature... anyways the release is already out, it's done, sorry if I bothered anyone ❤️

@ruyadorno ruyadorno merged commit 8806015 into latest Mar 4, 2021
@nlf nlf deleted the release/v7.6.1 branch March 28, 2022 20:49
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

Successfully merging this pull request may close these issues.

7 participants