@nodert-win11/windows.gaming.ui
Advanced tools
Comparing version 0.1.3 to 0.1.4
{ | ||
"name": "@nodert-win11/windows.gaming.ui", | ||
"version": "0.1.3", | ||
"version": "0.1.4", | ||
"description": "Use the Windows.Gaming.UI UWP API directly from Node.js", | ||
@@ -31,3 +31,3 @@ "main": "lib/main.js", | ||
}, | ||
"homepage": "https://github.com/demosjarco/NodeRT/tree/feature/136-vs2019", | ||
"homepage": "https://github.com/demosjarco/NodeRT/tree/vs2022", | ||
"author": "Generated by NodeRT (modified)", | ||
@@ -34,0 +34,0 @@ "contributors": [ |
@nodert-win11/windows.gaming.ui | ||
===== | ||
## Notice | ||
A Node.js wrapper for the <a href="http://msdn.microsoft.com/en-us/library/windows/apps/Windows.Gaming.UI.aspx" target="_blank">Windows.Gaming.UI</a> WinRT namespace, compatible with Windows 11 APIs. | ||
The series of `@nodert-win10-20h1` packages is unofficially-published NodeRT modules for **Windows 10 SDK, version 2004 (10.0.19041.0)** corresponding to Windows 10 Version 2004 (Codename 20H1 / May 2020 Update). | ||
These are generated by the modified version of NodeRT thus are experimental, as the original doesn't have support for 20H1 SDK, nor for building with VS2019. Supporting for VS2019 is based on <a href="https://github.com/NodeRT/NodeRT/pull/136" target="_blank">Taosenai's workaround with lxbndr's suggestion</a>. The modified source code can be found <a href="https://github.com/MaySoMusician/NodeRT/tree/feature/136-vs2019" target="_blank">here</a>. | ||
Below is the original description about this module. | ||
--- | ||
A Node.js wrapper for the <a href="http://msdn.microsoft.com/en-us/library/windows/apps/Windows.Gaming.UI.aspx" target="_blank">Windows.Gaming.UI</a> WinRT namespace, compatible with Windows 10 APIs. | ||
Using this module, you'll be able to consume the <a href="http://msdn.microsoft.com/en-us/library/windows/apps/Windows.Gaming.UI.aspx" target="_blank">Windows.Gaming.UI</a> API directly from Node.js. | ||
@@ -29,4 +19,4 @@ | ||
============ | ||
* Visual Studio 2019 and above. (Community edition works, other editions aren't tested but surely work!) | ||
* Python 2.7, 3.5, 3.6, 3.7, or 3.8 (for node-gyp) | ||
* Visual Studio version 2022 and above. (Express Desktop versions also work!) | ||
* Python 2.7 (for node-gyp) | ||
* <b>Important:</b> Updated versions of npm and node-gyp. (Note that the ones that are bundled with node might not be up to date). In order to install latest npm, run: | ||
@@ -50,3 +40,3 @@ ``` | ||
If you wish to rebuild this module using node-gyp, make sure to use the appropriate VS version using --msvs_version=2012/2013/2015/2017/2019 flag: | ||
If you wish to rebuild this module using node-gyp, make sure to use the appropriate VS version using --msvs_version=2012/2013/2015/2017 flag: | ||
@@ -57,5 +47,3 @@ For example: | ||
cd [module folder path] | ||
node-gyp rebuild --msvs_version=2019 | ||
``` | ||
If you fail to rebuild due to unable to find module 'nan', try running `npm install --ignore-scripts` | ||
node-gyp rebuild --msvs_version=2022 | ||
``` |
Sorry, the diff of this file is not supported yet
License Policy Violation
LicenseThis package is not allowed per your license policy. Review the package's license to ensure compliance.
Found 1 instance in 1 package
License Policy Violation
LicenseThis package is not allowed per your license policy. Review the package's license to ensure compliance.
Found 1 instance in 1 package
218717
46