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: nodejs/node-gyp
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: v11.1.0
Choose a base ref
...
head repository: nodejs/node-gyp
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: v11.2.0
Choose a head ref
  • 10 commits
  • 62 files changed
  • 7 contributors

Commits on Feb 19, 2025

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

Commits on Feb 20, 2025

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

Commits on Mar 19, 2025

  1. test: fix wasm test on Windows (#3145)

    * fix wasm test on windows
    
    * test not rely lint python
    toyobayashi authored Mar 19, 2025
    Configuration menu
    Copy the full SHA
    ee1d6fd View commit details
    Browse the repository at this point in the history

Commits on Apr 1, 2025

  1. Configuration menu
    Copy the full SHA
    3e1cdd4 View commit details
    Browse the repository at this point in the history
  2. Configuration menu
    Copy the full SHA
    4885110 View commit details
    Browse the repository at this point in the history
  3. fix: disable msbuild.exe nodeReuse (#3112)

    On windows, one may experience errors due to concurrent node-gyp calls (see #3095)
    
    When retrying after such a failure, retries are observed to fail repeatedly with strange
    EBUSY and EPERM errors. This turns out to be due to a caching feature where msbuild.exe
    will continue to run in the background (for either 15s or 15m depending on VS version),
    and keep open file handles to files and directories that the user may be trying to delete
    (for example with a new call to `npm ci`).
    
    This behavior is well documented, as is the recommended workaround implemented here.
    tmm1 authored Apr 1, 2025
    Configuration menu
    Copy the full SHA
    0cf16d2 View commit details
    Browse the repository at this point in the history
  4. Configuration menu
    Copy the full SHA
    80e9c79 View commit details
    Browse the repository at this point in the history
  5. fix: use maxRetries on fs.rm calls (#3113)

    * fix: remove more forcefully
    
    * add max retries to all fs.rm calls
    
    ---------
    
    Co-authored-by: Luke Karrys <[email protected]>
    tmm1 and lukekarrys authored Apr 1, 2025
    Configuration menu
    Copy the full SHA
    a2772a7 View commit details
    Browse the repository at this point in the history
  6. Configuration menu
    Copy the full SHA
    0ccbe7e View commit details
    Browse the repository at this point in the history
  7. Configuration menu
    Copy the full SHA
    fc557e4 View commit details
    Browse the repository at this point in the history
Loading