Spdlog bindings for Node.JS
Перейти к файлу
Robo e87949f6be
fix: swallow unhandled exceptions on shutdown (#47)
* fix: swallow unhandled exceptions on shutdown

* chore: bump 0.15.1
2024-10-30 09:08:13 +01:00
.vscode bump version (#41) 2023-10-23 23:41:51 +02:00
azure-pipelines chore: add APIScan fields (#45) 2024-02-28 12:44:12 -07:00
deps spdlog version update (#42) 2023-12-20 19:23:07 +00:00
src refactor: switch to node-addon-api (#43) 2024-01-31 12:32:03 -07:00
test spdlog version update (#42) 2023-12-20 19:23:07 +00:00
.clang-format style: consistent formatting with clang-format 2019-06-06 17:06:46 -07:00
.gitignore Update spdlog (#11) 2021-05-04 14:34:34 -07:00
.gitmodules use SPDLOG_PREVENT_CHILD_FD 2017-12-06 14:56:53 +01:00
LICENSE Initial commit 2017-11-28 12:01:36 -08:00
README.md Typo "Node.JS"→"Node.js" (#21) 2023-08-25 15:15:41 +09:00
SECURITY.md Microsoft mandatory file (#37) 2023-06-02 19:24:29 +00:00
binding.gyp fix: swallow unhandled exceptions on shutdown (#47) 2024-10-30 09:08:13 +01:00
index.d.ts expose log level 2022-10-24 15:43:55 +00:00
index.js chore: upgrade mkdirp to ^1.0.4 2022-11-30 21:43:33 +08:00
package-lock.json fix: swallow unhandled exceptions on shutdown (#47) 2024-10-30 09:08:13 +01:00
package.json fix: swallow unhandled exceptions on shutdown (#47) 2024-10-30 09:08:13 +01:00

README.md

node-spdlog

Spdlog bindings for Node.js

Build Status

Build Status

npm version

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.