Native node module to access the Windows Registry

Перейти к файлу

Raymond Zhao e202022091 1.0.7 (#14 )		2023-03-07 16:03:47 -08:00
.github/workflows	ci: update node version matrix	2022-03-03 19:09:14 +09:00
azure-pipelines	chore: use unified publishing pipeline (#12 )	2023-02-15 10:43:34 +09:00
lib	Convert to N-API (#3 )	2019-08-05 11:52:40 +02:00
src	Update src/winregistry.cc	2022-03-07 10:13:03 -08:00
test	add safe integer checks for malloc	2020-09-15 15:32:14 -07:00
.gitignore	initial commit	2019-02-20 17:21:51 +01:00
.npmignore	cleanup npm package	2022-01-25 14:36:48 +01:00
License.txt	initial commit	2019-02-20 17:21:51 +01:00
README.md	update readme for new name	2022-01-07 13:38:38 -08:00
binding.gyp	fix: use SpectreMitigation attribute (#13 )	2023-03-06 08:50:39 -08:00
package.json	1.0.7 (#14 )	2023-03-07 16:03:47 -08:00
tsconfig.json	initial commit	2019-02-20 17:21:51 +01:00
yarn.lock	upgrade mocha to fix dependabot issues	2022-01-07 13:33:23 -08:00

README.md

Native node module to access the Windows Registry

This module only has what is needed to support VS Code and is intended to be a lightweight module.

Installing

npm install @vscode/windows-registry

Using

var vsWinReg = require('vscode-windows-registry');
console.log(vsWinReg.GetStringRegKey('HKEY_LOCAL_MACHINE', 'SOFTWARE\\Microsoft\\Windows\\CurrentVersion', 'ProgramFilesPath');

Development

yarn
yarn node-gyp configure
yarn node-gyp build
yarn tsc
yarn test

License

MIT

Contributing

This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit https://cla.microsoft.com.

When you submit a pull request, a CLA-bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., label, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.

This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.