Skip to content
Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: npm/cli
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: v11.4.0
Choose a base ref
...
head repository: npm/cli
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: v11.4.1
Choose a head ref
  • 5 commits
  • 22 files changed
  • 6 contributors

Commits on May 16, 2025

  1. Configuration menu
    Copy the full SHA
    9cb9d50 View commit details
    Browse the repository at this point in the history

Commits on May 20, 2025

  1. Configuration menu
    Copy the full SHA
    8f6eb6b View commit details
    Browse the repository at this point in the history

Commits on May 21, 2025

  1. chore: remove references to skimdb.npmjs.com (#8314)

    # Summary
    With the public communication of the replication feed changes, this PR
    updates all documentation to remove references to skimdb.npmjs.com. All
    requests will be redirected to replicate.npmjs.com.
    
    
    ## References
    - https://github.com/orgs/community/discussions/152515
    -
    https://github.blog/changelog/2025-02-26-changes-and-deprecation-notice-for-npm-replication-apis/
    shmam authored May 21, 2025
    Configuration menu
    Copy the full SHA
    2f30251 View commit details
    Browse the repository at this point in the history
  2. docs: Clarify script working directory behavior (fixes #8305) (#8308)

    <!-- What / Why -->
    <!-- Describe the request in detail. What it does and why it's being
    changed. -->
    This pull request updates the documentation for npm scripts,
    specifically the `scripts.md` file.
    
    **What:**
    - Clarified that scripts are always run from the root of the package
    folder in npm v7 and later.
    - Added a "Historical Behavior in Older npm Versions" section to explain
    that while generally true for npm v6 and earlier, there were
    inconsistencies and that `process.cwd()` could be used as a safeguard.
    - Ensured the `INIT_CWD` environment variable is mentioned as a way for
    scripts to access the original working directory.
    - Provided links to the npm v7 release notes and the relevant GitHub
    issue discussing script working directory reliability in older versions.
    
    **Why:**
    This change aims to provide clearer and more accurate documentation
    regarding the working directory of npm scripts, addressing potential
    confusion, especially for users working with or migrating from older npm
    versions. This helps resolve the points raised in issue #8305.
    
    
    ## References
    <!-- Examples:
       Related to #0
       Depends on #0
       Blocked by #0
       Fixes #0
       Closes #0
    -->
    Fixes #8305
    
    ---------
    
    Co-authored-by: Michael Smith <owlstronaut@github.com>
    tarekwfa0110 and owlstronaut authored May 21, 2025
    Configuration menu
    Copy the full SHA
    3ed764a View commit details
    Browse the repository at this point in the history
  3. chore: release 11.4.1

    github-actions[bot] authored and owlstronaut committed May 21, 2025
    Configuration menu
    Copy the full SHA
    5d7a7a8 View commit details
    Browse the repository at this point in the history
Loading
pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy