From f9159ea2d994e14180fb02ab562f0119513e67cf Mon Sep 17 00:00:00 2001
From: 8cy <50817549+8cy@users.noreply.github.com>
Date: Fri, 3 Apr 2020 02:48:28 -0700
Subject: 2020/04/03, 02:47, V1.2.2

---
 node_modules/node-addon-api/doc/prebuild_tools.md | 16 ----------------
 1 file changed, 16 deletions(-)
 delete mode 100644 node_modules/node-addon-api/doc/prebuild_tools.md

(limited to 'node_modules/node-addon-api/doc/prebuild_tools.md')

diff --git a/node_modules/node-addon-api/doc/prebuild_tools.md b/node_modules/node-addon-api/doc/prebuild_tools.md
deleted file mode 100644
index 573af68..0000000
--- a/node_modules/node-addon-api/doc/prebuild_tools.md
+++ /dev/null
@@ -1,16 +0,0 @@
-# Prebuild tools
-
-The distribution of a native add-on is just as important as its implementation.
-In order to install a native add-on it's important to have all the necessary
-dependencies installed and well configured (see the [setup](setup.md) section).
-The end-user will need to compile the add-on when they will do an `npm install`
-and in some cases this could create problems. To avoid the compilation process it's
-possible to ditribute the native add-on in pre-built form for different platform
-and architectures. The prebuild tools help to create and distrubute the pre-built
-form of a native add-on.
-
-The following list report known tools that are compatible with **N-API**:
-
-- **[node-pre-gyp](https://www.npmjs.com/package/node-pre-gyp)**
-- **[prebuild](https://www.npmjs.com/package/prebuild)**
-- **[prebuildify](https://www.npmjs.com/package/prebuildify)**
-- 
cgit v1.2.3