-
-
Notifications
You must be signed in to change notification settings - Fork 528
Permalink
Choose a base ref
{{ refName }}
default
Choose a head ref
{{ refName }}
default
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/nan
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: v2.15.0
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
...
head repository: nodejs/nan
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: v2.16.0
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
- 8 commits
- 8 files changed
- 6 contributors
Commits on Dec 16, 2021
-
docs: license format and contributors
The license file differed enough that licensed did not recognize it. The link to the contributors was also outdated.
Configuration menu - View commit details
-
Copy full SHA for f9e63d6 - Browse repository at this point
Copy the full SHA f9e63d6View commit details
Commits on Jan 2, 2022
-
Configuration menu - View commit details
-
Copy full SHA for 96ed51a - Browse repository at this point
Copy the full SHA 96ed51aView commit details
Commits on Jan 3, 2022
-
Configuration menu - View commit details
-
Copy full SHA for 8db8c8f - Browse repository at this point
Copy the full SHA 8db8c8fView commit details
Commits on Apr 22, 2022
-
Failure to upgrade is causing a ton of pain at is:issue label:"ERR! node-gyp -v <= v5.1.0"
Configuration menu - View commit details
-
Copy full SHA for a866bb4 - Browse repository at this point
Copy the full SHA a866bb4View commit details
Commits on Apr 23, 2022
-
fix appveyor build tests when x86 binary is not available
As per Feodor Fitsner (Appveyor Support staff): > There is no x86 build of Node 18.x anymore, so you should [...] change it to: > > Update-NodeJsInstallation (Get-NodeJsLatestBuild $env:nodejs_version) x64 See Appveyor ticket: https://help.appveyor.com/discussions/problems/31957-please-install-nodejs-v18-new-builds-are-failing-looks-like-node-18-is-missing This fixes the following error: ``` Running Install scripts Update-NodeJsInstallation (Get-NodeJsLatestBuild $env:nodejs_version) Updating Node.js v18.0.0 (x86) Uninstalling Node.js v8.17.0 (x86)... Installing Node.js v18.0.0 (x86)... Exception calling "DownloadFile" with "2" argument(s): "The remote server returned an error: (404) Not Found." At C:\Program Files\AppVeyor\BuildAgent\Modules\nodejs-utils\nodejs-utils.psm1:58 char:5 + (New-Object Net.WebClient).DownloadFile($packageUrl, $packageFile ... + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : NotSpecified: (:) [], MethodInvocationException + FullyQualifiedErrorId : WebException IF %nodejs_version% LSS 4 npm -g install npm@2 IF %nodejs_version% EQU 5 npm -g install npm@3 set PATH=%APPDATA%\npm;%PATH% npm install 'npm' is not recognized as an internal or external command, operable program or batch file. Command exited with code 1 ```
Configuration menu - View commit details
-
Copy full SHA for 3aaaf1b - Browse repository at this point
Copy the full SHA 3aaaf1bView commit details -
Configuration menu - View commit details
-
Copy full SHA for 16fa322 - Browse repository at this point
Copy the full SHA 16fa322View commit details
Commits on May 25, 2022
-
Configuration menu - View commit details
-
Copy full SHA for 862939f - Browse repository at this point
Copy the full SHA 862939fView commit details -
Configuration menu - View commit details
-
Copy full SHA for 22c8ac4 - Browse repository at this point
Copy the full SHA 22c8ac4View commit details
Loading
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff v2.15.0...v2.16.0